[Python-Dev] 2.0 Release Plans

[Tim Peters]

PythonLabs had a high-decibel meeting today (well, Monday), culminating in
Universal Harmony.  Jeremy will be updating PEP 200 accordingly.  Just three
highlights:

+ The release schedule has Officially Slipped by one week:  2.0b1 will ship
a week from this coming Monday.  There are too many Open and Accepted
patches backed up to meet the original date.  Also problems cropping up,
like new std tests failing to pass every day (you're not supposed to do
that, you know!  consider yourself clucked at), and patches having to be
redone because of other patches getting checked in.  We want to take the
extra week to do this right, and give you more space to do *your* part
right.

+ While only one beta release is scheduled at this time, we reserve the
right to make a second beta release if significant problems crop up during
the first beta period.  Of course that would cause additional slippage of
2.0 final, if it becomes necessary.  Note that "no features after 2.0b1 is
out!" still stands, regardless of how many beta releases there are.

+ I changed the Patch Manager guidelines at

     http://python.sourceforge.net/sf-faq.html#a1

to better reflect the way we're actually using the beast.  In a nutshell,
Rejected has been changed to mean "this patch is dead, period"; and Open
patches that are awaiting resolution of complaints should remain Open.

All right.  Time for inspiration.  From my point of view, you've all had
waaaaaay too much sleep in August!  Pull non-stop all-nighters until 2.0b1
is out the door, or go work on some project for sissies -- like Perl 6.0 or
the twelve thousandth implementation of Scheme <wink>.

no-guts-no-glory-slow-and-steady-wins-the-race-ly y'rs  - tim