We have had a few changes in turbogears 2 in the last couple betas, and I'm excited about the new features that were added. But we have to quit adding new stuff to TG2 and get a release out the door. And we have to have a solid, tested, documented, tg2 release for PyCon so that we can market the heck out of TG there.
So, from now on any major change in code (even if it does not change published API's) must be proposed via a trac ticket, and should be reviewed and approved before it's added. And after monday, this feature freeze will become even more strict, and we'll need a patch in trac, and explicit approval from either me or Florent before any non-bugfix code goes into tg2. We'll also be more strict about testing dependencies before we allow new versions into the index. As soon as we release 2.0 rc1 I'll split off a 2.0 branch, and 2.1 development can continue in trunk. But we will have a at least a full week of feature freeze between b6 and rc1 -- but the feature freeze may be longer if for some reason we have to do a b7 release. And for those of you who've been on beta upgrade tredmill thanks for your patience! I think the result will be worth it. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
