On Sun, Feb 8, 2009 at 1:02 PM, Mark Ramm <[email protected]> wrote: > > We keep moving forward, not as fast as we'd hoped, but pretty darned > quickly. But we need to keep up the pace for another few weeks in > order to have a clean, solid, well polished release before PyCon 2009. > I want to market the heck out of TG2 in the runup to pycon, and show > off all the great work that's been done at the conference, and that > means we have a hard deadline to meet. > > So, here is my proposal. > > We're at beta 5 now, beta 6 should be _the_last_beta. After b6 we > should start doing release candidates. Currently b6 is scheduled to > be a "friday the 13th" release, but I would not be suppressed to see > it pushed back to the 16th -- but it would be bad if we pushed it back > any further than that. Hopefully we will have just one or two RC's > and have TG2 in a releasable state by early march. > > We would then have a 100% feature freeze after b6, so any features not > completed by then will be removed, and no new features will be added. > > At risk of removal/not being added are the following features: > > * Out of the box support for Jinja templates > * Creation of TG2 apps as zip safe eggs (regular eggs will work fine!) > > And we have one incomplete feature which I think can be allowed to > block the release: > > * Out of the box support for Internationalization of TW and FormEncode > > This one has a patch, which looks good to me, but I really want > someone with more internationalization experience to take a look at it > before we add it in. > > Beyon the feature freeze, b6 being the final beta means that we need > to close all the high or higher tickets in the b6 milestone on track: > > http://bit.ly/nn8z > > And any bugfix or feature that would potentially change any API must > be on the b6 list, and should be marked high priority. I don't know > that the above list is definitive at the moment, but it is a start. > If there's anything that's a critical code change it needs to have a > ticket, be assigned to milestone beta 6, and be marked as high or > higher priority. > > If there's something important to you, which needs to be in 2.0 it > needs to have a ticket, and be added to the above list. > > What do you all think?
I had a rough start of the week, and will have a complex weekend (I got visits) so I think I won't make the 13th cut (after all that's bad luck) But I do think my remaining open issues will be in by the 16th. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
