[Python-Dev] peps: describe the current policy
Georg Brandl
g.brandl at gmx.net
Mon Oct 1 19:40:40 CEST 2012
More information about the Python-Dev mailing list
Mon Oct 1 19:40:40 CEST 2012
- Previous message: [Python-Dev] [Python-checkins] peps: 3.2 and 3.3 release schedules: add information on bugfix releases and release
- Next message: [Python-Dev] Daily DMG builds
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/01/2012 07:38 PM, benjamin.peterson wrote: > http://hg.python.org/peps/rev/641add9f9542 > changeset: 4530:641add9f9542 > user: Benjamin Peterson <benjamin at python.org> > date: Mon Oct 01 13:38:31 2012 -0400 > summary: > describe the current policy > > files: > pep-0373.txt | 8 ++++++++ > 1 files changed, 8 insertions(+), 0 deletions(-) > > > diff --git a/pep-0373.txt b/pep-0373.txt > --- a/pep-0373.txt > +++ b/pep-0373.txt > @@ -49,6 +49,14 @@ > Maintenance releases > ==================== > > +Being the last of the 2.x series, 2.7 will have an extended period of > +maintenance. The current plan is to support it for at least 5 years > +from the initial 2.7 release. This means there will be bugfix releases > +until 2015. Depending on Python 3 adoption, this may be modified up or > +down. TBH, I would guarantee it for at least 5 years: the current wording is not an improvement over the current situation as it basically does not tell anything definite. Georg
- Previous message: [Python-Dev] [Python-checkins] peps: 3.2 and 3.3 release schedules: add information on bugfix releases and release
- Next message: [Python-Dev] Daily DMG builds
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list