[Product-Developers] conventions on version numbering

[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 incompatible API changes, * MINOR
>> version when you add functionality in a backwards-compatible 
>> manner, and

This classification is completely nonsense. There had been always
some incompatible changes API wise and import-wise between 4.x versions.

- -aj

- -- 
ZOPYX Limited         | Python | Zope | Plone | E-Publishing
Hundskapfklinge 33    | Consulting & Development
D-72074 Tübingen      | Electronic Publishing Solutions
www.zopyx.com         | Scalable Web Solutions
- --------------------------------------------------
Produce & Publish - www.produce-and-publish.com


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJSceyOAAoJEADcfz7u4AZjU/sLv27sWUZZaW5w2gyQbdkb8+8s
11gClsiVeTxzfPlIwHvYmibDlKk3nkqonB1xQjf0wGB/m51NJZ6Kq9lKqvnNYFS9
A1h1jRjbuBS782Hjz5BW58jEBPkK6AacHQVzJIpUa6DfMveouoNtQa9TfewlZRF2
iwptfnTGANpHL6bjKJT4HSnRTxgF20epPYvE9jUupfdR8x3aEFJO8+/OqP/HRSbb
pdRngMQ6qEAPElWHm5eNKHwPcsMxm8QqJQJCuG5Mzl1hP0YbSrGCSb798xsN8aA7
8c3kfbPzGq5XyoBs3OrFEDHIF6q22uZaM79NSqsdDBTkE17Jv0HSXiG3WE+4fp9H
FJlCsfjnZIcl7x1tmvE/2GeRBqQULJiyzqnHq113uONAYx4PbZIFXf3mHrEpCWk/
c9EKwxKYOIceaZa+5ym3xCXOILm6Q87+y2W0qetbGrEVKARRHCjcYlNdQ/DZixOO
OttNb2B/j7o6bNRVkaqfrcOR122RuyM=
=rVw1
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lists.vcf
Type: text/x-vcard
Size: 353 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20131031/e436d40f/attachment.vcf>