I am considering producing a Python 2.3.6 release, which would of course only be a bug fix maintenance release. The primary reason is that not all OS distributions have upgraded to Python 2.4 and I think it's worthwhile for us to bless a release that fixes known critical bugs. I'm willing to be the release manager for 2.3.6, but I'm hoping you all will be able to help identify the most important bugs that need fixing. First, is there interest in getting a 2.3.6 release out? I'd propose keeping things simple, by picking a date and releasing what we've got at that date (assuming of course all the unit tests pass). It's probably a good idea to add a wiki page tracking the fixes we want to get in there. 2.5 final is slated for 12-Sep-2006 and I know that Anthony is planning for a 2.4.4 soon after that. I'm thinking that we'd try to do a 2.3.6 a couple of weeks after 2.4.4 so that people who care about it aren't stacked up with fixing too many branches at once. My first thought was to shoot for Monday October 9th. What are the potential 2.3.6 fixes? Nothing on this page: http://www.python.org/download/releases/2.3.5/bugs/ seems critical to me. I know that I've added some important email package fixes that are already in Subversion. There are tons of bugs and patches reported against 2.3 in SF (lament: why won't SF just / tell/ me how many there are?), but I have no idea atm which, if any, are important enough to go into a 2.3.6. I haven't yet done an svn diff to see what changes are already in there. I don't have the cycles to fix things myself, so it would be up to everyone to help commit fixes. I'll ride herd a bit if necessary. Thoughts? I don't want to waste my time if nobody thinks a 2.3.6 would be useful, but I'm happy to do it if there's community support. I'll also need the usual help with Windows installers and documentation updates. Cheers, -Barry
Barry Warsaw wrote:
I am considering producing a Python 2.3.6 release, which would of course only be a bug fix maintenance release. The primary reason is that not all OS distributions have upgraded to Python 2.4 and I think it's worthwhile for us to bless a release that fixes known critical bugs. I'm willing to be the release manager for 2.3.6, but I'm hoping you all will be able to help identify the most important bugs that need fixing.
First, is there interest in getting a 2.3.6 release out? I'd propose keeping things simple, by picking a date and releasing what we've got at that date (assuming of course all the unit tests pass). It's probably a good idea to add a wiki page tracking the fixes we want to get in there.
2.5 final is slated for 12-Sep-2006 and I know that Anthony is planning for a 2.4.4 soon after that. I'm thinking that we'd try to do a 2.3.6 a couple of weeks after 2.4.4 so that people who care about it aren't stacked up with fixing too many branches at once. My first thought was to shoot for Monday October 9th.
What are the potential 2.3.6 fixes? Nothing on this page:
http://www.python.org/download/releases/2.3.5/bugs/
seems critical to me. I know that I've added some important email package fixes that are already in Subversion. There are tons of bugs and patches reported against 2.3 in SF (lament: why won't SF just /tell/ me how many there are?), but I have no idea atm which, if any, are important enough to go into a 2.3.6.
Most of them are also in the 2.4 releases...
I haven't yet done an svn diff to see what changes are already in there.
There's one problem: it was thought for a long time that there wouldn't be any more 2.3 releases, so bug fixes were applied only in the head and 2.4 branch. If there will be a 2.3.6, it might be necessary to look at all 2.4 branch fixes and decide which of them are worth backporting. Georg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 29, 2006, at 11:29 AM, Georg Brandl wrote:
There's one problem: it was thought for a long time that there wouldn't be any more 2.3 releases, so bug fixes were applied only in the head and 2.4 branch.
If there will be a 2.3.6, it might be necessary to look at all 2.4 branch fixes and decide which of them are worth backporting.
Right, we'll definitely have to do that, and maybe not much more. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRPSmuXEjvBPtnXfVAQKyegQAgpzLpPddKE03wg3orKvlHPJXFKpbaLvd 4gIRIgvqwGjKwjxY4s8Gn55axHJM8YBwJ+IbCzYg3nmBB3JvljuKNxTZtz4w781Y BS/apc8Ng+2wv/W8Eo2zVbbRformZa24H/d8Gq5Mdst1yTrcAwwcO7k1hHjAl9w8 HFIWjechAVg= =4wXb -----END PGP SIGNATURE-----
Barry Warsaw <barry@python.org> wrote:
I am considering producing a Python 2.3.6 release, which would of course only be a bug fix maintenance release. The primary reason is that not all OS distributions have upgraded to Python 2.4 and I think it's worthwhile for us to bless a release that fixes known critical bugs. I'm willing to be the release manager for 2.3.6, but I'm hoping you all will be able to help identify the most important bugs that need fixing.
What are the potential 2.3.6 fixes? Nothing on this page:
These are both issues in 2.3 and 2.4: http://www.python.org/sf/780714 http://www.python.org/sf/1548687 Those are all I have off the top of my head. - Josiah
Barry Warsaw schrieb:
Thoughts? I don't want to waste my time if nobody thinks a 2.3.6 would be useful, but I'm happy to do it if there's community support. I'll also need the usual help with Windows installers and documentation updates.
I personally would consider it a waste of time. Since it wouldn't waste *my* time, I'm -0 :-) I think everybody has arranged with whatever quirks Python 2.3 has. Distributors of Python 2.3 have added whatever patches they think are absolutely necessary. Making another release could cause confusion; at worst, it may cause people to special-case people for 2.3.6 in case the release contains some incompatible change that affects existing applications. Regards, Martin
On Sep 9, 2006, at 2:10 PM, Martin v. Löwis wrote:
Barry Warsaw schrieb:
Thoughts? I don't want to waste my time if nobody thinks a 2.3.6 would be useful, but I'm happy to do it if there's community support. I'll also need the usual help with Windows installers and documentation updates.
I personally would consider it a waste of time. Since it wouldn't waste *my* time, I'm -0 :-)
I think everybody has arranged with whatever quirks Python 2.3 has. Distributors of Python 2.3 have added whatever patches they think are absolutely necessary. Making another release could cause confusion; at worst, it may cause people to special-case people for 2.3.6 in case the release contains some incompatible change that affects existing applications.
Well, there certainly hasn't been an overwhelming chorus of support for the idea, so I think I'll waste my time elsewhere ;). Consider the offer withdrawn. -Barry
Barry Warsaw <barry@python.org> wrote:
Well, there certainly hasn't been an overwhelming chorus of support for the idea, so I think I'll waste my time elsewhere ;). Consider the offer withdrawn.
I hope someone tries to fix one of the two bugs I listed that were problems for 2.3 and 2.4 in 2.4.4: http://www.python.org/sf/780714 http://www.python.org/sf/1548687 The former involves stack allocation errors in subthreads that exists even in 2.5, which may not be fixable in Windows, and very likely is not fixable on linux. The latter is fixable on all platforms. - Josiah
participants (4)
-
"Martin v. Löwis" -
Barry Warsaw -
Georg Brandl -
Josiah Carlson