I'm working this week to finish up TW/tw.forms 0.9.6 and sprox 0.6 and I'm nearly finished. I have 1 more tutorial to write for sprox (that's right, sprox tutorials!) and I have some other low-hanging fruit dangling from tw to clean up before it goes. I want tgext.admin and tgext.crud to rely on tw0.9.6 and sprox 0.6, so that is the only blocker I see.
Can you express what you mean by: "make sure all works properly" I think we need some exit criteria. Sorry for pushing so hard on 2.1. It's just that 2.1's codebase is much cleaner and easier to support, and y'all know I spend a bit of time on IRC. And I agree, we need to release 2.0 to pypi if all the dependent eggs are there. If not, then we need to put some pressure on our constituents. cheers. -chris On Jun 2, 10:50 am, Florent Aide <[email protected]> wrote: > On Fri, May 29, 2009 at 8:37 PM, percious <[email protected]> wrote: > > > I for one would like 2.1 out as soon as practical. I think the > > component architecture can wait until 2.2. I feel that the 2.1 > > codebase is very well tested and definitely stable enough for an alpha > > release, so let's get 'er done! > > Guys, > > I am in favor of a regular release cycle with small changes in each, > so that we can document the changes and the upgrade path, so I would > say: "Let's prepare 2.1 release and make sure all works properly... if > so then release it at the end of next week" > > But we should also take care to have some pypi release one day or > another because only tg1 is installable from the pypi ATM. > > Florent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
