Updated release schedule, added some notes for PEP 101 (Doing Python releases).
This commit is contained in:
Larry Hastings
parent
620f079ec8
commit
133d0a80ca
27
pep-0101.txt
27
pep-0101.txt
|
|
@ -24,6 +24,31 @@ Abstract
|
|||
is organized as a recipe and you can actually print this out and check
|
||||
items off as you complete them.
|
||||
|
||||
Things You'll Need
|
||||
|
||||
As a release manager there are a lot of resources you'll need to access.
|
||||
Here's a hopefully-complete list.
|
||||
|
||||
* A GPG key.
|
||||
|
||||
Python releases are digitally signed with GPG; you'll need a key,
|
||||
which hopefully will be on the "web of trust" with at least one of
|
||||
the other release managers.
|
||||
|
||||
* Access to ``dinsdale.python.org``, the Python web host. You'll
|
||||
be uploading files directly here.
|
||||
|
||||
* Write access to the website SVN repository
|
||||
|
||||
Instructions here:
|
||||
|
||||
http://www.python.org/dev/pydotorg/website/
|
||||
|
||||
* Write access to the PEP repository.
|
||||
|
||||
If you're reading this, you probably already have this--the first
|
||||
task of any release manager is to draft the release schedule. But
|
||||
in case you just signed up... sucker! I mean, uh, congratulations!
|
||||
|
||||
How to Make A Release
|
||||
|
||||
|
|
@ -140,7 +165,7 @@ How to Make A Release
|
|||
___ Regenerate Lib/pydoc-topics.py.
|
||||
|
||||
cd to the Doc directory and type ``make pydoc-topics``. Then copy
|
||||
``build/pydoc-topics/pydoc-topics.py`` to ``../Lib/pydoc_topics.py``.
|
||||
``build/pydoc-topics/topics.py`` to ``../Lib/pydoc_data/topics.py``.
|
||||
|
||||
___ Check the docs for markup errors.
|
||||
|
||||
|
|
|
|||
47
pep-0429.txt
47
pep-0429.txt
|
|
@ -34,26 +34,32 @@ Release Manager and Crew
|
|||
Release Schedule
|
||||
================
|
||||
|
||||
The anticipated schedule:
|
||||
The releases so far:
|
||||
|
||||
- 3.4.0 alpha 1: August 3, 2013
|
||||
- 3.4.0 alpha 2: August 31, 2013
|
||||
- 3.4.0 alpha 3: September 28, 2013
|
||||
- 3.4.0 alpha 4: October 19, 2013
|
||||
- 3.4.0 beta 1: November 23, 2013
|
||||
|
||||
The anticipated schedulefor future releases:
|
||||
|
||||
- 3.4.0 alpha 2: September 8, 2013
|
||||
- 3.4.0 alpha 3: September 29, 2013
|
||||
- 3.4.0 alpha 4: October 20, 2013
|
||||
- 3.4.0 beta 1: November 24, 2013
|
||||
|
||||
(Beta 1 is also "feature freeze"--no new features beyond this point.)
|
||||
|
||||
- 3.4.0 beta 2: January 4, 2014
|
||||
- 3.4.0 candidate 1: January 18, 2014
|
||||
- 3.4.0 candidate 2: February 1, 2014
|
||||
- 3.4.0 final: February 22, 2014
|
||||
- 3.4.0 beta 2: January 45 2014
|
||||
- 3.4.0 candidate 1: January 19, 2014
|
||||
- 3.4.0 candidate 2: February 2, 2014
|
||||
- 3.4.0 final: February 23, 2014
|
||||
|
||||
.. don't forget to update final date above as well
|
||||
|
||||
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.
|
||||
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 existance of any release-blocking issues.
|
||||
|
||||
|
||||
Features for 3.4
|
||||
|
|
@ -61,7 +67,10 @@ Features for 3.4
|
|||
|
||||
Implemented / Final PEPs:
|
||||
|
||||
* None so far
|
||||
* PEP 435, a standardized "enum" module
|
||||
* PEP 442, improved semantics for object finalization
|
||||
* PEP 443, adding single-dispatch generic functions to the standard library
|
||||
* PEP 445, a new C API for implementing custom memory allocators
|
||||
|
||||
Other final large-scale changes:
|
||||
|
||||
|
|
@ -69,17 +78,19 @@ Other final large-scale changes:
|
|||
|
||||
Candidate PEPs:
|
||||
|
||||
* PEP 395: Qualified Names for Modules
|
||||
* PEP 3143: Standard daemon process library
|
||||
* PEP 3154: Pickle protocol version 4
|
||||
* PEP 431, improved support for time zone databases
|
||||
* PEP 436, a build-time preprocessor for builtin argument parsing
|
||||
* PEP 446, explicit controls on file descriptor inheritance
|
||||
* PEP 447, support for __locallookup__ metaclass method
|
||||
* PEP 448, additional unpacking generalizations
|
||||
* PEP 3154, Pickle protocol revision 4
|
||||
|
||||
Other proposed large-scale changes:
|
||||
|
||||
* New packaging libraries, possibly deprecating "distutils"
|
||||
* Introspection information for builtins
|
||||
* Addition of the "regex" module
|
||||
* Email version 6
|
||||
* A standard event-loop interface
|
||||
* Breaking out standard library and docs into separate repos
|
||||
|
||||
Deferred to post-3.4:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue