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? johannes > > -aj > > > hvelarde wrote > > according to our versioning scheme conventions, we should do the > > following: > > > > Given a version number MAJOR.MINOR.PATCH, increment the: > > > > * MAJOR version when you make incompatible API changes, > > * MINOR version when you add functionality in a backwards-compatible > > manner, and > > * PATCH version when you make backwards-compatible bug fixes. > > > > http://semver.org/ > > > > how do you handle the inclussion of a new translation on a package? do > > you release as a patch or as a minor version number change? > > > > best regards > > -- > > Héctor Velarde > > > > > > > > _______________________________________________ > > Product-Developers mailing list > > > [email protected] > > > https://lists.plone.org/mailman/listinfo/plone-product-developers > > > > > > smime.p7s (5K) > > <http://plone.293351.n2.nabble.com/attachment/7568580/0/smime.p7s> > > > hvelarde wrote > > according to our versioning scheme conventions, we should do the > > following: > > > > Given a version number MAJOR.MINOR.PATCH, increment the: > > > > * MAJOR version when you make incompatible API changes, > > * MINOR version when you add functionality in a backwards-compatible > > manner, and > > * PATCH version when you make backwards-compatible bug fixes. > > > > http://semver.org/ > > > > how do you handle the inclussion of a new translation on a package? do > > you release as a patch or as a minor version number change? > > > > best regards > > -- > > Héctor Velarde > > > > > > > > _______________________________________________ > > Product-Developers mailing list > > > [email protected] > > > https://lists.plone.org/mailman/listinfo/plone-product-developers > > > > > > smime.p7s (5K) > > <http://plone.293351.n2.nabble.com/attachment/7568580/0/smime.p7s> > > > > > > -- > View this message in context: > http://plone.293351.n2.nabble.com/conventions-on-version-numbering-tp7568580p7568581.html > Sent from the Product Developers mailing list archive at Nabble.com. > _______________________________________________ > Product-Developers mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-product-developers -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: [email protected] web: http://programmatic.pro http://bluedynamics.com
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
