[Product-Developers] conventions on version numbering
Andreas Jung
lists at zopyx.com
Thu Oct 31 07:31:01 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Ledermann wrote:
> On Thu, Oct 31, 2013 at 9:48 AM, Andreas Jung <lists at zopyx.com>
> wrote:
>
>
> Christian Ledermann wrote:
>>>> On Thu, Oct 31, 2013 at 8:37 AM, Andreas Jung
>>>> <lists at 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:
>>>>>>>>
>>>>>>>> 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.
>>>>
>>>>> yes that's why this discussion is happening. We can learn
>>>>> from previous mistakes ;)
> Here is the real definition:
>
> MAJOR: the next big thing and we intentionally break things in a
> large way
>
> MINOR: we break imports, we are _trying_ to be as compatible as
> possible
>
> PATCH: only bugfixes, no API changes, no new features
>
>> :D sad but true, room for improvement
Import changes are usually not a problem - they can fixed easily.
API changes happen rarely - usually not a big problem.
The problem are changes in the behavior methods - intentionally
or not - this is the major pain when it comes to migrations.
At least I had two major issues with a weird behavior of
plone.outputfilters and traversal issues with plone.app.imaging URLs
with a customer migration 4.0 to 4.2 - the issues have been so weird
that it was hard and at some point to time consuming to debug the real
problem in Plone. I ended up building workarounds in my application code
(more maintainable, less time consuming).
- -aj
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQGUBAEBAgAGBQJScgc0AAoJEADcfz7u4AZjoRILv0BZPJjJ0aHYC6WX7M5NAPSt
g8FIqJ3Jm2S4WpLNGbhPKFweBveIfskDPYUyIiUeSxYXsPwh2kUE2EHfV0Qgl4od
tRz/JbChljpIVb2Tf7CbpbRVV0BAZRQe/ihN3oYv6P82H/NmCFch2O+U64MhmPu1
9xmb9xXttdkvYv5D4L2ZsrLly/JE8HnGZ7igrnFPUBw3l1f+ySR+pYAx4BV4su0A
zScn4qGsFc07WNjx9BYMStwbSldzKIuXFEG+6l98MGFwc0hH/r+Y4N04SmawihwA
fxLLtN/e33SkSgm8PqG6r20kkgljB0AmOwLP3AHMSqzBhPLWV323ppPmKrKQsROx
qByYOC1MlUB6hbe22xTdcsX+2jII7kog8qhjBX/xQTaKAVS0JCo8MPYt9In7arj9
qRGqJdVRC7KD0DMbMdjEs0VHee5P/ixLtfsSMZVNL7xPgqsCHIpXsnxf4bTXHJoZ
Mz9578xwoZNs/CJaMX7cDQvsttyQkUY=
=hbVy
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lists.vcf
Type: text/x-vcard
Size: 368 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20131031/08419276/attachment.vcf>
More information about the Product-Developers
mailing list