[Python-Dev] Maintaining old releases

Aahz aahz at pythoncraft.com
Fri Aug 15 05:29:23 CEST 2008

On Thu, Aug 14, 2008, M.-A. Lemburg wrote:
> On 2008-08-14 08:43, Martin v. L?wis wrote:
>>>For example, let's project dates for closing 2.6 and 3.0 now, and add
>>>them to PEP 361.
>>My view is that they should be closed when 2.7 and 3.1 are released.
> Since we don't have a fixed release cycle, making the 2.(n-1)
> maintenance time frame depend on the 2.n release is not a reliable way
> of defining the 2.(n-1) lifetime.
> Instead, we should fix the dates based on the 2.(n-1) release date.

Why?  As Brett pointed out, we simply don't have the infrastructure to
maintain multiple releases -- if we force time-based maintenance, it
won't work.
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

Adopt A Process -- stop killing all your children!

More information about the Python-Dev mailing list