[Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn. (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Mon Jan 9 22:59:07 CET 2012
- Previous message: [Python-Dev] Python C API: Problem sending tuple to a method of a python Class
- Next message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 09 Jan 2012 21:58:29 +0100 terry.reedy <python-checkins at python.org> wrote:
-Different branches are used at a time to represent different minor versions -in which development is made. All development should be done first in the -:ref:
in-development <indevbranch>branch, and selectively backported -to other branches when necessary. +There is a branch for each minor version. Development is done separately +for Python 2 and Python 3. For each major version, each change should be made +first in the oldest branch to which it applies and forward-ported as +appropriate.
Please avoid using the terms "minor version" and "major version", they are confusing.
Thanks
Antoine.
- Previous message: [Python-Dev] Python C API: Problem sending tuple to a method of a python Class
- Next message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]