The final update to PEP 429, the Python 3.4 release schedule. (I think!)
This commit is contained in:
parent
3f74d9be74
commit
8f9830c6db
21
pep-0429.txt
21
pep-0429.txt
|
@ -34,7 +34,7 @@ Release Manager and Crew
|
|||
Release Schedule
|
||||
================
|
||||
|
||||
The releases so far:
|
||||
The releases:
|
||||
|
||||
- 3.4.0 alpha 1: August 3, 2013
|
||||
- 3.4.0 alpha 2: September 9, 2013
|
||||
|
@ -45,27 +45,10 @@ The releases so far:
|
|||
- 3.4.0 beta 3: January 26, 2014
|
||||
- 3.4.0 candidate 1: February 10, 2014
|
||||
- 3.4.0 candidate 2: February 23, 2014
|
||||
|
||||
(Beta 1 is also "feature freeze"--no new features beyond this point.)
|
||||
|
||||
The anticipated schedule for future releases:
|
||||
|
||||
- 3.4.0 candidate 3: March 9, 2014
|
||||
- 3.4.0 final: March 16, 2014
|
||||
|
||||
.. don't forget to update final date above as well
|
||||
|
||||
These are the days we expect to release the software;
|
||||
Python core developers should note that the revision
|
||||
used for the release will generally be "tagged" the day
|
||||
before. However the actual availability of the release
|
||||
for download on python.org depends on the schedules of
|
||||
the crew and the existence of any release-blocking issues.
|
||||
|
||||
Since posting the original schedule, we've added "beta 3" and slipped
|
||||
the subsequent releases by three weeks. This is because of last-minute
|
||||
changes due to adoption of "Argument Clinic". The extra beta will
|
||||
give these changes extra time to mature.
|
||||
(Beta 1 was also "feature freeze"--no new features beyond this point.)
|
||||
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue