updates
This commit is contained in:
parent
a7c0ec55a3
commit
901d21d134
10
pep-0101.txt
10
pep-0101.txt
|
@ -64,9 +64,13 @@ How to Make A Release
|
||||||
This helps by performing several automatic editing steps, and guides you
|
This helps by performing several automatic editing steps, and guides you
|
||||||
to perform some manual editing steps.
|
to perform some manual editing steps.
|
||||||
|
|
||||||
___ Impose a check-in freeze. Send a message to
|
___ Impose a check-in freeze. Send a message to these mailing lists:
|
||||||
python-dev@python.org (Py3: and python-3000@python.org) telling people
|
* python-committers@python.org
|
||||||
not to make any check-ins on the tree until further notice.
|
* python-dev@python.org
|
||||||
|
* (Py3: python-3000@python.org)
|
||||||
|
|
||||||
|
telling people not to make any check-ins on the tree until further
|
||||||
|
notice.
|
||||||
|
|
||||||
At this point, nobody except the RM or his duly assigned agents should
|
At this point, nobody except the RM or his duly assigned agents should
|
||||||
make any commits to the branches. The assigned agents are either from
|
make any commits to the branches. The assigned agents are either from
|
||||||
|
|
|
@ -56,7 +56,7 @@ Release Schedule
|
||||||
May 08 2008: Python 2.6a3 and 3.0a5 are released
|
May 08 2008: Python 2.6a3 and 3.0a5 are released
|
||||||
Jun 18 2008: Python 2.6b1 and 3.0b1 are released
|
Jun 18 2008: Python 2.6b1 and 3.0b1 are released
|
||||||
Jul 17 2008: Python 2.6b2 and 3.0b2 are released
|
Jul 17 2008: Python 2.6b2 and 3.0b2 are released
|
||||||
Aug 20 2008: Python 2.6b3 and 3.0b3 planned
|
Aug 20 2008: Python 2.6b3 and 3.0b3 are released
|
||||||
Sep 03 2008: Python 2.6rc1 and 3.0rc1 planned
|
Sep 03 2008: Python 2.6rc1 and 3.0rc1 planned
|
||||||
Sep 17 2008: Python 2.6rc2 and 3.0rc2 planned
|
Sep 17 2008: Python 2.6rc2 and 3.0rc2 planned
|
||||||
Oct 01 2008: Python 2.6 and 3.0 final planned
|
Oct 01 2008: Python 2.6 and 3.0 final planned
|
||||||
|
|
Loading…
Reference in New Issue