3.2 and 3.3 release schedules: add information on bugfix releases and release lifespan.
This commit is contained in:
Georg Brandl
parent
9c83bacdff
commit
ccaa14aa75
84
pep-0392.txt
84
pep-0392.txt
|
|
@ -13,11 +13,13 @@ Python-Version: 3.2
|
|||
Abstract
|
||||
========
|
||||
|
||||
This document describes the development and release schedule for
|
||||
Python 3.2. The schedule primarily concerns itself with PEP-sized
|
||||
items. Small features may be added up to and including the first beta
|
||||
release. Bugs may be fixed until the final release, which is planned
|
||||
for February 2011.
|
||||
This document describes the development and release schedule for the
|
||||
Python 3.2 series. The schedule primarily concerns itself with PEP-sized
|
||||
items.
|
||||
|
||||
.. Small features may be added up to and including the first beta
|
||||
release. Bugs may be fixed until the final release, which is planned
|
||||
for February 2011.
|
||||
|
||||
|
||||
Release Manager and Crew
|
||||
|
|
@ -29,30 +31,67 @@ Release Manager and Crew
|
|||
- Documentation: Georg Brandl
|
||||
|
||||
|
||||
3.2 Lifespan
|
||||
============
|
||||
|
||||
3.2 will receive bugfix updates approximately every 4-6 months until
|
||||
one release after the release of 3.3.0 final. After that, security
|
||||
updates (source only) will be released until 5 years after the release
|
||||
of 3.2 final, which will be February 2016.
|
||||
|
||||
|
||||
Release Schedule
|
||||
================
|
||||
|
||||
The current schedule is:
|
||||
3.2 schedule
|
||||
------------
|
||||
|
||||
- 3.2 alpha 1: August 1, 2010
|
||||
- 3.2 alpha 2: September 4, 2010
|
||||
- 3.2 alpha 3: October 9, 2010
|
||||
- 3.2 alpha 4: November 13, 2010
|
||||
- 3.2 beta 1: December 4, 2010
|
||||
- 3.2 alpha 2: September 6, 2010
|
||||
- 3.2 alpha 3: October 12, 2010
|
||||
- 3.2 alpha 4: November 16, 2010
|
||||
- 3.2 beta 1: December 6, 2010
|
||||
|
||||
(No new features beyond this point.)
|
||||
|
||||
- 3.2 beta 2: December 18, 2010
|
||||
- 3.2 candidate 1: January 15, 2011
|
||||
- 3.2 candidate 2: January 29, 2011
|
||||
- 3.2 candidate 3: February 12, 2011
|
||||
- 3.2 final: February 19, 2011
|
||||
- 3.2 beta 2: December 20, 2010
|
||||
- 3.2 candidate 1: January 16, 2011
|
||||
- 3.2 candidate 2: January 31, 2011
|
||||
- 3.2 candidate 3: February 14, 2011
|
||||
- 3.2 final: February 20, 2011
|
||||
|
||||
.. don't forget to update final date above as well
|
||||
|
||||
Every release day listed here is a Saturday; the actual availability
|
||||
of the release for download on python.org will depend on the schedules
|
||||
of the crew.
|
||||
3.2.1 schedule
|
||||
--------------
|
||||
|
||||
- 3.2.1 beta 1: May 8, 2011
|
||||
- 3.2.1 candidate 1: May 17, 2011
|
||||
- 3.2.1 candidate 2: July 3, 2011
|
||||
- 3.2.1 final: July 11, 2011
|
||||
|
||||
3.2.2 schedule
|
||||
--------------
|
||||
|
||||
- 3.2.2 candidate 1: August 14, 2011
|
||||
- 3.2.2 final: September 4, 2011
|
||||
|
||||
3.2.3 schedule
|
||||
--------------
|
||||
|
||||
- 3.2.3 candidate 1: February 25, 2012
|
||||
- 3.2.3 candidate 2: March 18, 2012
|
||||
- 3.2.3 final: April 11, 2012
|
||||
|
||||
3.2.4 schedule
|
||||
--------------
|
||||
|
||||
- 3.2.4 beta 1: planned for Oct/Nov 2012
|
||||
- 3.2.4 candidate 1: following two weeks after beta 1
|
||||
- 3.2.4 final: following two weeks after candidate 1, if no further RC
|
||||
are necessary
|
||||
|
||||
-- Only security releases after 3.2.4 --
|
||||
|
||||
|
||||
Features for 3.2
|
||||
|
|
@ -64,15 +103,6 @@ syntax and no additions to the builtins may be made.
|
|||
No large-scale changes have been recorded yet.
|
||||
|
||||
|
||||
Bugfix Releases
|
||||
===============
|
||||
|
||||
- 3.2.1: released July 10, 2011
|
||||
- 3.2.2: released September 4, 2011
|
||||
|
||||
- 3.2.3: planned February 10-17, 2012
|
||||
|
||||
|
||||
References
|
||||
==========
|
||||
|
||||
|
|
|
|||
50
pep-0398.txt
50
pep-0398.txt
|
|
@ -15,9 +15,11 @@ Abstract
|
|||
|
||||
This document describes the development and release schedule for
|
||||
Python 3.3. The schedule primarily concerns itself with PEP-sized
|
||||
items. Small features may be added up to and including the first beta
|
||||
release. Bugs may be fixed until the final release, which is planned
|
||||
for September 2012.
|
||||
items.
|
||||
|
||||
.. Small features may be added up to and including the first beta
|
||||
release. Bugs may be fixed until the final release, which is planned
|
||||
for September 2012.
|
||||
|
||||
|
||||
Release Manager and Crew
|
||||
|
|
@ -29,30 +31,48 @@ Release Manager and Crew
|
|||
- Documentation: Georg Brandl
|
||||
|
||||
|
||||
3.3 Lifespan
|
||||
============
|
||||
|
||||
3.3 will receive bugfix updates approximately every 4-6 months until
|
||||
one release after the release of 3.4.0 final. After that, security
|
||||
updates (source only) will be released until 5 years after the release
|
||||
of 3.3.0 final, which will be September 2017.
|
||||
|
||||
|
||||
Release Schedule
|
||||
================
|
||||
|
||||
The schedule was:
|
||||
3.3.0 schedule
|
||||
--------------
|
||||
|
||||
- 3.3.0 alpha 1: March 3, 2012
|
||||
- 3.3.0 alpha 2: April 1, 2012
|
||||
- 3.3.0 alpha 1: March 5, 2012
|
||||
- 3.3.0 alpha 2: April 2, 2012
|
||||
- 3.3.0 alpha 3: May 1, 2012
|
||||
- 3.3.0 alpha 4: May 26, 2012
|
||||
- 3.3.0 beta 1: June 26, 2012
|
||||
- 3.3.0 alpha 4: May 31, 2012
|
||||
- 3.3.0 beta 1: June 27, 2012
|
||||
|
||||
(No new features beyond this point.)
|
||||
|
||||
- 3.3.0 beta 2: August 11, 2012
|
||||
- 3.3.0 candidate 1: August 25, 2012
|
||||
- 3.3.0 candidate 2: September 8, 2012
|
||||
- 3.3.0 candidate 3: September 22, 2012
|
||||
- 3.3.0 beta 2: August 12, 2012
|
||||
- 3.3.0 candidate 1: August 24, 2012
|
||||
- 3.3.0 candidate 2: September 9, 2012
|
||||
- 3.3.0 candidate 3: September 24, 2012
|
||||
- 3.3.0 final: September 29, 2012
|
||||
|
||||
.. don't forget to update final date above as well
|
||||
|
||||
Every release day listed here was the prospective day of tagging the release;
|
||||
the actual availability of the release for download on python.org depends
|
||||
on the schedules of the crew.
|
||||
.. Every release day listed here is the prospective day of tagging the release;
|
||||
the actual availability of the release for download on python.org depends
|
||||
on the schedules of the crew.
|
||||
|
||||
3.3.1 schedule
|
||||
--------------
|
||||
|
||||
- 3.3.1 beta 1: planned for Oct/Nov 2012
|
||||
- 3.3.1 candidate 1: following two weeks after beta 1
|
||||
- 3.3.1 final: following two weeks after candidate 1, if no further RC
|
||||
are necessary
|
||||
|
||||
|
||||
Features for 3.3
|
||||
|
|
|
|||
Loading…
Reference in New Issue