Now it's official. The developer teams has decided against a Python 3.0.2 bugfix release [1]. Python 3.0 will not see another release and everybody should move to Python 3.1 as soon as possible. The 3.1 release is so much better than 3.0 and the list of incompatibilities is small. Have fun!
[1] Barry Warsaw, Python 3.0 (pinin' for the fjords)
Abonnieren
Kommentare zum Post (Atom)
I've long suspected Python's release planning is lacking and its release and branch engineering is a swell. This is a part proof. Isn't there a branch of lots of maintenance fixes that went into Python 3.1 that could just be applied to Python 3.0 to make a last release? Normally it's not so hard.
AntwortenLöschenAre you sure it's lacking? The last security release of Python 2.4 just came out. Python 2.5 is going to get security fixes for at least one more year, possible two. We are currently maintaining Python 2.6 + 3.1 and developing 2.7 + 3.2.
AntwortenLöschenPython 3.0 is the only exception from the general release rules because it's a special and experimental release. The development team has agreed upon pulling the plug. So far no user of 3.1 has complained.