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. 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. The MAJOR.MINOR.x-rxxxx are development snapshots: automatically generated snapshots from the subversion repository (exported every Thursday/Friday depending on your timezone). They are not official releases, but a convenience for people who want to keep up to date, or test any bug fixes that are relevant to them, and who may not have, or want, subversion experience. Hope this helps. Duncan P.S. I would guess, but I wasn't here so I don't know, that the changes probably happened with the switchover from some previous source code control system (cvs?) to subversion. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
