Re: [Python-Dev] status of 2.5

2008-10-07 Thread Antoine Pitrou
Raymond Hettinger rcn.com> writes: > > The 2.6/3.0 development process was so disruptive that I doubt > that 2.5 received adequate attention for bug fixes. Why not wait > two or three months for the dust to settle? I know that I, and a couple of others, have tried to backport "important" bug fi

Re: [Python-Dev] status of 2.5

2008-10-07 Thread Martin v. Löwis
> ISTM, that 3.0 and 2.6 backports have consumed substantial developer > attention over the last few months. Sure - but who is going to sit down and study the commit logs, to do backporting? Unless someone specifically volunteers to do that (with a specific timeline when he will start, and when he

Re: [Python-Dev] status of 2.5

2008-10-06 Thread Terry Reedy
Martin v. Löwis wrote: Neal Norwitz wrote: Should we plan to put out a final 2.5 release? If so, should we continue to backport fixes (like Martin's removal of Alpha in setup.py)? My preference is that we do put out a final 2.5 that has all accumulated bug fixes. Then close the branch. That

Re: [Python-Dev] status of 2.5

2008-10-06 Thread Raymond Hettinger
[A.M. Kuchling] Can you please clarify your meaning? Do you mean that * we haven't been backporting fixes to 2.5? Unsure. I surely have given zero attention to 2.5. * we should wait to see if any horrible problems are reported in 2.6? Yes. That would be a great idea. * we need to look

Re: [Python-Dev] status of 2.5

2008-10-06 Thread A.M. Kuchling
On Mon, Oct 06, 2008 at 12:53:01PM -0700, Raymond Hettinger wrote: > The 2.6/3.0 development process was so disruptive that I doubt > that 2.5 received adequate attention for bug fixes. Why not wait > two or three months for the dust to settle? Can you please clarify your meaning? Do you mean tha

Re: [Python-Dev] status of 2.5

2008-10-06 Thread Martin v. Löwis
> The 2.6/3.0 development process was so disruptive that I doubt > that 2.5 received adequate attention for bug fixes. Why not wait > two or three months for the dust to settle? Would it receive more attention in the next three months? Who specifically would give it that attention? Regards, Mart

Re: [Python-Dev] status of 2.5

2008-10-06 Thread Martin v. Löwis
Neal Norwitz wrote: > Should we plan to put out a final 2.5 release? If so, should we > continue to backport fixes (like Martin's removal of Alpha in > setup.py)? My preference is that we do put out a final 2.5 that has > all accumulated bug fixes. Then close the branch. That way if we put > ou

Re: [Python-Dev] status of 2.5

2008-10-06 Thread Raymond Hettinger
[Neal Norwitz] Should we plan to put out a final 2.5 release? If so, should we continue to backport fixes (like Martin's removal of Alpha in setup.py)? My preference is that we do put out a final 2.5 that has all accumulated bug fixes. Then close the branch. That way if we put out a security

Re: [Python-Dev] status of 2.5

2008-10-06 Thread skip
Neal> Should we plan to put out a final 2.5 release? I'm probably a bad person to ask. At work we are still using 2.4. :-/ Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http

[Python-Dev] status of 2.5

2008-10-06 Thread Neal Norwitz
Should we plan to put out a final 2.5 release? If so, should we continue to backport fixes (like Martin's removal of Alpha in setup.py)? My preference is that we do put out a final 2.5 that has all accumulated bug fixes. Then close the branch. That way if we put out a security release for 2.5,