[Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn. (original) (raw)
Rob Cliffe rob.cliffe at btinternet.com
Tue Jan 10 09:49:04 CET 2012
- Previous message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Next message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
But "minor version" and "major version" are readily understandable to the general reader, e.g. me, whereas "feature release" and "release series" I find are not. Couldn't the first two terms be defined once and then used throughout? Rob Cliffe
On 10/01/2012 04:05, Terry Reedy wrote:
On 1/9/2012 8:52 PM, Nick Coghlan wrote:
On Tue, Jan 10, 2012 at 7:59 AM, Antoine Pitrou<solipsis at pitrou.net> wrote:
Please avoid using the terms "minor version" and "major version", they are confusing.
Indeed. "Feature release" (2.7, 3.2, 3.3) and "release series" (2.x, 3.x) are the least confusing terms we have available. I minimally edited what was already there to correct what is now an error. The change comes immediately after a section defining major, minor, and micro releases. To change terms, http://docs.python.org/devguide/devcycle.html and possibly other pages needs more extensive editing.
- Previous message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Next message: [Python-Dev] devguide: Backporting is obsolete. Add details that I had to learn.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]