[Python-Dev] 2.0 Release Plans

[Tim Peters]

[MAL]
> Does this mean I can still splip in that minor patch to allow
> for attribute doc-strings in 2.0b1 provided I write up a short
> PEP really fast ;-) ?

2.0 went into feature freeze the Monday *before* this one!  So, no.  The "no
new features after 2.0b1" refers mostly to the patches currently in Open and
Accepted:  if *they're* not checked in before 2.0b1 goes out, they don't get
into 2.0 either.

Ideas that were accepted by Guido for 2.0 before last Monday aren't part of
the general "feature freeze".  Any new feature proposed *since* then has
been Postponed without second thought.  Guido accepted several ideas before
feature freeze that still haven't been checked in (in some cases, still not
coded!), and just dealing with them has already caused a slip in the
schedule.  We simply can't afford to entertain new ideas too now (indeed,
that's why "feature freeze" exists:  focus).

For you in particular <wink>, how about dealing with Open patch 100899?
It's been assigned to you for 5 weeks, and if you're not going to review it
or kick /F in the butt, assign it to someone else.

> BTW, what the new standard on releasing ideas to dev public ?
> I know I'll have to write a PEP, but where should I put the
> patch ? Into the SF patch manager or on a separate page on the
> Internet ?

The PEP should be posted to both Python-Dev and comp.lang.python after its
first stab is done.  If you don't at least post a link to the patch in the
SF Patch Manager, the patch doesn't officially exist.  I personally prefer
one-stop shopping, and SF is the Python Developer's Mall; but there's no
rule about that yet (note that 100899's patch was apparently so big SF
wouldn't accept it, so /F *had* to post just a URL to the Patch Manager).