On Jan 22, 2008 8:47 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > While the exact release schedule for 2.5.2 is still up in the air, I > expect that it will be within a few weeks. This means that we need to > make sure that anything that should go into 2.5.2 goes in ASAP, > preferably this week. It also means that we should be very careful > what goes in though -- and we should be paying particular attention to > stability on all platforms! Fortunately it looks like quite a few 2.5 > buildbots are green: http://python.org/dev/buildbot/2.5/ > > I propose that anything that ought to go into 2.5.2 (or should be > reviewed for suitability to go into it) should be marked "urgent" in > the tracker, *and* have its version set to (or include) "Python 2.5". > > Also, *nothing* should go into the 2.4 branch any more *except* > important security patches. If we're doing a security release, it'll > most likely be a source-only release, and it will differ from 2.4.4 > only in that it will have some new security patches defined. > > A reminder: 2.5.2 should only get bugfixes, new features.
If Guido felt like dragging the time machine out he would catch his mistake and have that say "NO new features". -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
