[MTOS-dev] How should we test MTOS compatibility?

Chad Everett sixapart.2007 at everitz.com
Fri Dec 14 05:51:33 PST 2007


As to this particular problem (the upgrade one), it's likely been 
fixed.  Brad checked in a fix for bug 64072 (the one I reported) last 
night and I just ran an upgrade with the latest nightly (r1116) this 
morning, from my 3.35 install.  I haven't tried from 4.0 or 4.01, but 
Chris said he did last night.  I suspect it should take care of the 
upgrade problem that others were seeing.

This probably won't be in the commercial beta available by download, but 
if that's what you're testing, you can get the fix here:

http://code.sixapart.com/trac/movabletype/browser/branches/boomer/lib/MT/Upgrade.pm?rev=1116

You could also take the latest nightly (r1116) and install the 
commercial pack from the commercial beta if you'd rather take that 
route.  But that's probably not a "recommended" solution.  So forget I 
mentioned it.  But it does appear to work.  :)



Bud Gibson wrote:
> Thank you all for your muted responses :).  Please note that I was 
> asking a protocol question, not actually reporting a bug.
>
> On Dec 14, 2007 3:38 AM, Byrne Reese < byrne at sixapart.com 
> <mailto:byrne at sixapart.com>> wrote:
>
>     +1
>
>     Could not agree more – this list is NOT for bug reports.
>
>     BTW – the bug you describe has been fixed, and the nightlies for
>     tonight contain the fix. :)
>
>
>     On 12/13/07 2:38 PM, "Chad Everett" <sixapart.2007 at everitz.com
>     <mailto:sixapart.2007 at everitz.com>> wrote:
>
>         I would suggest reporting it as a bug.  The more feedback they
>         get, the more likely it is to be reproduced (and eventually
>         fixed).
>
>         As responsive as the list may be, it's not a bug reporting
>         system - official or otherwise.
>
>         I think the problem a lot of folks (myself included) have with
>         a list being used for support or bug reporting is that the
>         bugs never get filed.  If they don't get filed they won't get
>         fixed.
>
>         As to this one, I filed one this morning and have received
>         feedback on it already.  Chris was also able to reproduce the
>         error.
>
>         Send them the error you are getting and the steps it takes to
>         reproduce it in as much detail as possible.  Screenshots can
>         even help.
>
>
>         Bud Gibson wrote:
>
>             I have now successfully installed MTOS.  But, in the
>             process, I was unable to upgrade a database from MT4RC4
>             days.  Perhaps this is a forums question (where I
>             currently cannot post), but from a larger dev perspective,
>             what's the protocol for talking about these things?
>
>
>
>         ------------------------------------------------------------------------
>         _______________________________________________
>         MTOS-dev mailing list
>         MTOS-dev at sixapart.com <mailto:MTOS-dev at sixapart.com>
>         http://www.sixapart.com/mailman/listinfo/mtos-dev
>
>
>
>     _______________________________________________
>     MTOS-dev mailing list
>     MTOS-dev at sixapart.com <mailto:MTOS-dev at sixapart.com>
>     http://www.sixapart.com/mailman/listinfo/mtos-dev
>
>
>
>
> -- 
> Bud Gibson
> cell:  734-657-4800
> web:  http://michiganinnovators.org <http://michiganinnovators.org> 

-- 
Chad Everett
Everitz Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.sixapart.com/pipermail/mtos-dev/attachments/20071214/0e3269e8/attachment.html 


More information about the MTOS-dev mailing list