Re: [Product-Developers] conventions on version numbering

2013-10-31 Thread Christian Ledermann
On Thu, Oct 31, 2013 at 8:37 AM, Andreas Jung li...@zopyx.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Glick (Plone) wrote: On 10/30/13, 12:17 PM, Héctor Velarde wrote: according to our versioning scheme conventions, we should do the following: Given a version number

Re: [Product-Developers] conventions on version numbering

2013-10-31 Thread Andreas Jung
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Ledermann wrote: On Thu, Oct 31, 2013 at 8:37 AM, Andreas Jung li...@zopyx.com wrote: David Glick (Plone) wrote: On 10/30/13, 12:17 PM, Héctor Velarde wrote: according to our versioning scheme conventions, we should do the following:

Re: [Product-Developers] conventions on version numbering

2013-10-31 Thread Christian Ledermann
I can feel your pain and am +1 with you on that my personal experience is that 4.2 to 4.3 is more painful than i expected :( On Thu, Oct 31, 2013 at 10:31 AM, Andreas Jung li...@zopyx.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Ledermann wrote: On Thu, Oct 31, 2013

[Product-Developers] conventions on version numbering

2013-10-30 Thread Héctor Velarde
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

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread ajung
Our versioning schema refers to Plone? -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

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread David Glick (Plone)
On 10/30/13, 12:17 PM, Héctor Velarde 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

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread Héctor Velarde
HV this is the Plone Product Developers, isn't it? http://developer.plone.org/reference_manuals/external/plone.api/contribute/conventions.html#versioning-scheme see what happens when you miss a Plone Conference? Héctor Velarde On 30-10-2013 17:26, ajung wrote: Our versioning schema refers to

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread Guido Stevens
On 30 okt. 2013, at 21:00, Johannes Raggam raggam...@adm.at wrote: 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.

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread Guido Stevens
Oops correction: 1.2.3dev 1.2.3rc1 1.2.3rc1 = 1.2.3.rc1 = 1.2.3-rc1 = 1.2.3.c rc = .rc = -rc = c dev follows c So using .dev as if it were equal or before alpha is faulty. A dev release is between beta and final. -- Guido Stevens | +31.43.3618933 | http://cosent.nl s o c i a l k

Re: [Product-Developers] conventions on version numbering

2013-10-30 Thread Andreas Jung
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Glick (Plone) wrote: On 10/30/13, 12:17 PM, Héctor Velarde 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