Johannes Raggam schreef op 30-10-13 21:00:
On Mit, 2013-10-30 at 12:26 -0700, ajung wrote:
"Our" versioning schema refers to Plone?
This one, which should become the Plone coding conventions:
https://github.com/plone/plone.api/blob/master/docs/contribute/conventions.rst#versioning-scheme
I'd do a PATCH increment. But if a package only has MINOR increments, a
MINOR is also OK, IMO.
semver.org says: "Bug fixes not affecting the API increment the patch
version, backwards compatible API additions/changes increment the minor
version, and backwards incompatible API changes increment the major
version."
Regarding versioning schemes: Comparing the versioning scheme section
described in conventions.rst, which I wrote and the scheme described on
http://semver.org/ - there are some differences regarding pre-release
versions. They require pre-release versions to be seperated by a hyphen,
like "1.2.3-rc1". I tend to use "1.2.3rc1" or "1.2.3dev" for this.
And then, the hitchhikers guide suggests again something different:
"1.2.3.rc1"
http://guide.python-distribute.org/specification.html#development-releases
Any suggestions or any experiences, how setuptools compares versions?
For me, and I think setuptools too, PEP 386 is leading:
http://www.python.org/dev/peps/pep-0386/#the-new-versioning-algorithm
--
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl
_______________________________________________
Product-Developers mailing list
product-develop...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-product-developers
