Jacob Kaplan-Moss wrote: > > On Nov 20, 2005, at 3:15 PM, Adrian Holovaty wrote: > >> On 11/20/05, Robert Wittams >> <[EMAIL PROTECTED]> wrote: >> >>> Ok. Now that we have the 0.9 release, shall we merge new-admin, and >>> people who are worried about short term stability can just stick with >>> the release? >>> >>> Then, after it has stabilised in trunk, we can release a 0.91 with >>> new-admin included. >> >> >> Great plan. Jacob had a list of a couple of other things to include in >> 0.91, but I don't recall what they were. I think transactions might've >> been on the list. (What were they, Jacob?) > > > This is my rough stab at a roadmap towards 1.0, but it's very rough: > > 0.91: "core API" changes: transactions, OR, multi-threaded MySQL, > subclassing fix > 0.92: "admin fixes": new-admin, kill core fields > 0.93: "code complete": fix any other *code* changes (AJAX, schema > evolution, etc.) > 1.0rc1: "documentation complete": all docs completed > 1.0: outstanding bug fixes, screencasts :) > > If it would be easier to merge new-admin before the other stuff that > would be just fine with me; I just sketched this out as a plan of > attack to keep our attentions focused. I'd say if new-admin is ready > we should switch 0.91 and 0.92 above. > > Jacob > I think thats a good set of features, but I would change the order a little (just because of what I have done and what I think is already done by others atm)
maybe 0.91: new-admin 0.92: transactions, OR stuff (hugo has these in reasonable shape so should be good to go) 0.93: core fields, subclassing (this is what I'm doing at the moment) Beyond that, the same as you. I've killed any plans for schema evolution pre 1.0, thats for later ;-) Robert
