[Python-Dev] Re: RELEASED Python 2.3.1 (original) (raw)

Tim Peters tim.one at comcast.net
Fri Sep 26 14:24:27 EDT 2003

[Jeremy Hylton]

We should treat 2.3.1 like 2.3.1rc1 and aim for Sep. 30 for a 2.3.2.

[Anthony Baxter]

Wouldn't it be better to cut a 2.3.2rc before the final 2.3.2?

once-bitten-ly,

Well, Jeremy's "Sep. 30" is only 4 days away. If 2.3.2 is restricted to fixing just the obvious big problems already reported against 2.3.1, in reality it's like Jeremy said: 2.3.1 was really 2.3.2c1 <0.5 wink>.

Don't get too gun-shy. There were lots of changes in who did what for the 2.3.1 release, and some glitches were inevitable. It had gotten so smooth with the same people doing the same things all the time that, e.g., you must have noticed that Guido stopped doing anything for releases. I would have liked to pay a lot more attention but just couldn't make time for it; I'm sure the same is true of the other PythonLabs alumni (including Guido). So some things could have gone better. It's not that big a deal -- next time they will go better. Remember that we pioneered all possible ways to screw up a release already, and discovered that it's a finite set .

More information about the Python-Dev mailing list