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
I don't find 'major' and 'minor' confusing too. Maybe because it is the
designation used in linux community for years.
On Tue, Jan 10, 2012 at 7:49 PM, Rob Cliffe rob.cli...@btinternet.comwrote:
But minor version and major version are readily understandable to the
general reader, e.g. me,
On Jan 10, 2012, at 09:03 PM, Anthony Kong wrote:
I don't find 'major' and 'minor' confusing too. Maybe because it is the
designation used in linux community for years.
Neither do I. I read them as aliases for leftmost digit and middle digit
respectively, regardless of Python's interpretation
On Tue, 10 Jan 2012 08:49:04 +
Rob Cliffe rob.cli...@btinternet.com wrote:
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
On Jan 10, 2012, at 7:57 AM, Antoine Pitrou wrote:
On Tue, 10 Jan 2012 08:49:04 +
Rob Cliffe rob.cli...@btinternet.com wrote:
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.
http://semver.org/
This has made sense since Gentoo days.
On Tue, Jan 10, 2012 at 11:57 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 10 Jan 2012 08:49:04 +
Rob Cliffe rob.cli...@btinternet.com wrote:
But minor version and major version are readily understandable to
the general
On Tue, 10 Jan 2012 11:57:03 -0500
Glyph gl...@twistedmatrix.com wrote:
Whatever your personal feelings, there is a precedent established in the API:
sys.version_info.major
2
sys.version_info.minor
7
sys.version_info.micro
1
This strikes me as the most authoritative definition of
On 1/10/2012 12:14 PM, Antoine Pitrou wrote:
I changed the terminology in my latest changeset:
http://hg.python.org/devguide/rev/f39d063ab3dd
Important to notice is that the major / minor distinction isn't
relevant in most contexts, while the feature / bugfix distinction is.
Where major plays
On Mon, 09 Jan 2012 21:58:29 +0100
terry.reedy python-check...@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
On Tue, Jan 10, 2012 at 7:59 AM, Antoine Pitrou solip...@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.
Cheers,
Nick.
--
On 1/9/2012 8:52 PM, Nick Coghlan wrote:
On Tue, Jan 10, 2012 at 7:59 AM, Antoine Pitrousolip...@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
11 matches
Mail list logo
