[Python-Dev] Maintaining old releases

M.-A. Lemburg mal at egenix.com
Wed Aug 13 16:07:43 CEST 2008

On 2008-08-13 15:20, Steve Holden wrote:
> M.-A. Lemburg wrote:
>> Perhaps we should just document the maintenance of Python releases
>> more clearly and also plan for a final bug fix release 3 years after
>> the initial branch release. That way developers and users can also
>> adjust their plans accordingly.
> As always the problem is getting someone to do this not insignificant 
> amount of work.

We'd just have to add a section to the release schedule PEP:

Release Maintenance

    Bug fix releases will be made available until September 19, 2009.
    The following bug fix releases have been posted:

        2.5.1: February 22, 2008
        2.5.2: April 18, 2007

    Security fix releases will continue to be made available as
    necessary until September 19, 2011. No further updates will
    be posted after that date. The following security fix releases
    have been posted:

        No security fix releases have been released.

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Aug 13 2008)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/

:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::

    eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
     D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
            Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the Python-Dev mailing list