iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add a more concrete release schedule.

This commit is contained in:
Guido van Rossum 2003-01-07 02:23:50 +00:00
parent 070e5cfa2e
commit f7f1408a1e
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-0283.txt
View File

@ -15,10 +15,6 @@ Abstract
items. Small features may be added until the first beta release. items. Small features may be added until the first beta release.
Bugs may be fixed until the final release. Bugs may be fixed until the final release.
There is currently no complete schedule. I plan to release alpha
1 in 2002, and hope for a final release in the second quarter of
2003.
There will be at least two alpha releases, two beta releases, and There will be at least two alpha releases, two beta releases, and
one release candidate. Alpha and beta releases will be spaced at one release candidate. Alpha and beta releases will be spaced at
least 4 weeks apart (except if an emergency release must be made least 4 weeks apart (except if an emergency release must be made
@ -26,6 +22,16 @@ Abstract
release does not count). Release candidates will be spaced at release does not count). Release candidates will be spaced at
least one week apart (excepting again blunder corrections). least one week apart (excepting again blunder corrections).
Based on the first alpha release, which was made on Dec. 31, 2002,
here's a fairly aggressive release schedule that follows the above
guidelines:
alpha 2 -- late January
beta 1 -- late February
beta 2 -- late March
rc 1 -- late April
final -- early May
Release Manager Release Manager