[mapserver-dev] [Motion] Version Numbering

Ed Nash edward.nash at gmx.de
Mon Oct 15 06:30:07 PDT 2012


I know this has been previously discussed, but I have one question
which I don't think I've yet seen answered: how do you note a major
version change (API or Mapfile breaking change) with the Year.Month
version scheme (e.g. the change from version 5 to 6 in which lots of
deprecated items &c. were (eventually and rightly) dropped)?

It's not a major problem in the grand scheme of things, but as it is
then you know that a move from "5.6" to "6.0" will probably be
painful, whereas "6.0" to "6.2" less so: comparing "09.10." to "11.04"
or "11.04" to "12.10" then there's no obvious hint that one of them is
actually a major version change.

If I could think of an elegant solution to the problem then I'd
suggest it! Maybe the version number for a new major version (breaking
API / Mapfile changes) could be pre- or suffixed in some way?



On Mon, Oct 15, 2012 at 9:40 AM, thomas bonfort
<thomas.bonfort at gmail.com> wrote:
> Devs,
> We've discussed this previously but never formally voted on our
> version numbering.
> Context: In order to allow some decoupling between mapserver, mapcache
> and tinyows releases, we will be changing our version numbering from
> Major.Minor.Release to Year.Month[.Release], i.e. 6.2.0, 6.2.1,
> 6.2.2,..., 6.4.0, 6.4.1,...  will be released as 12.10, 12.10.1,
> 12.10.2..., 13.04, 13.04.1,...
> I motion to release our coming version as 12.10 and adopt a
> Year.Month[.Release] for future versions.
> +1
> thomas
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev

More information about the mapserver-dev mailing list