On May 3, 2010, at 12:16 AM, Duncan Gibson wrote:
> Emil:
>> Version numbering rules are not respected at all:
>> "MAJOR.MINOR.PATCH
>> MAJOR.MINORbBUILD
>> MAJOR.MINORrcBUILD"
>>
>> But all versions are named something like MAJOR.MINOR.x-rxxxx.
>> First of all r was not specified in the specifications.
>> Second, it does not look like the rules specifies.
>
> MAJOR.MINOR.PATCH is used, eg FLTK-1.1.10
> NoteL within the MAJOR.MINOR series the API and ABI are fixed.
>
> MAJOR.MINORbBUILD has not been used in the few years I've been
> following FLTK. My guess would be that it relates to snapshots.
No, "b" mean "beta", as in:
1.3b1 First beta release for 1.3
1.3rc1 First release candidate for 1.3
1.3.0 First production/stable release for 1.3
> MAJOR.MINOR.rcBUILD has not been used, but if I remember correctly
> we have MAJOR.MINOR.PATCHrcX where X is 1, 2 or 3, for the release
> candidates before the official release of MAJOR.MINOR.PATCH.
There have been a few instances for 1.1.x where we've done release candidates
for patch updates due to the number of changes, however in general we've just
pushed out a patch update when it is convenient and not needed an extra release
candidate just for a patch (which is supposed to be small bug fixes...)
________________________________________
Michael Sweet, Easy Software Products
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
