[mapserver-dev] [motion] enter 6.2 release cycle

[Lime, Steve D (DNR)]

> - How do we deal with version number ?

I favor the year/month approach across components. I think that's what was talked about way back when... 

>   - Do we want/can provide a single configure/make process for the MS Suite ?

Agreed, unnecessary IMHO.

Steve

-----Original Message-----
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of thomas bonfort
Sent: Monday, July 02, 2012 10:28 AM
To: Olivier Courtin
Cc: mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] [motion] enter 6.2 release cycle

I'll reply with my mapcache hat on:

On Fri, Jun 29, 2012 at 9:30 PM, Olivier Courtin <olivier.courtin at oslandia.com> wrote:
> On Jun 29, 2012, at 3:18 PM, thomas bonfort wrote:
>
> Thomas,
>
>> Motion passed !
>
> Great !
>
> I guess, that astyling and branches policies also apply to MapCache 
> and TinyOWS.

I have applied the astyle formatting convention to the mapcache code.

>
>
> Still 2 questions on the MS Suite release:
>   - How do we deal with version number ?

My preference would be to release mapcache as a 1.0 for now, as releasing it as 6.2 seems awkward. If and when we decide to number the mapserver versions with a YY.MM version number, then the numbering schema would be homogeneous between components.

>
>   - Do we want/can provide a single configure/make
>     process for the MS Suite ?
For mapcache this is not a requirement nor even desirable. How about for tinyows ?

--
thomas
>
> O.
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev