[mapserver-dev] [Motion] Version Numbering

Stephen Woodbridge woodbri at swoodbridge.com
Mon Oct 15 11:44:27 PDT 2012


Yes, this is my memory of this also. I would support this numbering for 
"MapServer Suite" but the individual packages should retain the 
major.minor[.version] numbering.

-Steve W.

On 10/15/2012 2:21 PM, Daniel Morissette wrote:
> If I remember correctly the last time we discussed this we could not get
> consensus on the change, and one suggestion was that we could use this
> new numbering for the "MapServer Suite", but continue to use the
> traditional version numbers for the individual components (i.e.
> MapServer CGI, MapScript, MapCache and TinyOWS).
>
> So if we went that route then we'd release "MapServer Suite 12.10" which
> is composed of:
>
> - MapServer CGI and MapScript 6.2
> - MapCache 1.0 (?)
> - TinyOWS 1.0 (?)
>
> This way we could present a unified suite and still allow each
> individual component to maintain its own point release cycle which is
> what I believe was the main concern against the unified version numbers.
>
> Daniel
>
>
> On 12-10-15 3:40 AM, thomas bonfort 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