[gdal-dev] Motion: Release next major GDAL version as GDAL/OGR 1.10

Etienne Tourigny etourigny.dev at gmail.com
Mon Nov 12 12:35:36 PST 2012


+1 for 1.10

Etienne

On Mon, Nov 12, 2012 at 6:26 PM, Howard Butler <hobu.inc at gmail.com> wrote:
> +0 Howard
>
> I don't like that we're changing the version macro and changing our versioning pattern 10+ years down the road. Assumptions about GDAL_VERSION_NUM are likely baked in many places, and this is going to cause some (albeit minor) pain.
>
> There's no right way though, it's just a choice. My personal preference is to call it 2.0.
>
> Howard
>
> On Nov 12, 2012, at 1:54 PM, Frank Warmerdam <warmerdam at pobox.com> wrote:
>
>> +1 Frank
>>
>>
>> On Fri, Nov 9, 2012 at 12:10 PM, Even Rouault <even.rouault at mines-paris.org> wrote:
>> Motion: The next major GDAL version released from trunk will be called
>> GDAL/OGR 1.10.
>>
>> To take into account 2-figure numbers in the components of the version number,
>> the GDAL_VERSION_NUM macro will be changed accordingly as :
>>
>> #  define GDAL_VERSION_NUM
>> (GDAL_VERSION_MAJOR*1000000+GDAL_VERSION_MINOR*10000+GDAL_VERSION_REV*100+GDAL_VERSION_BUILD)
>>
>> A new macro will be added so that users don't have to do all the above
>> multiplications :
>>
>> #define GDAL_COMPUTE_VERSION(maj,min,rev)
>> (maj*1000000+min*10000+rev*100)
>>
>> (Note: as raised by Mateusz, I've dropped the 'build' argument in the macro,
>> since it has never been used in the past and it is unlikely code would depend
>> on that)
>>
>> ----
>>
>> Hi,
>>
>> Not surprisingly when it is related to preferences on version numbering, the
>> previous discussion thread has not lead to a clear consensus on the topic, but
>> we need to make a decision soon so that users can anticipate the adaptations
>> needed in their code.
>>
>> 1.10 seems the more logical option to me, even if that implies changing the
>> way we compute GDAL_VERSION_NUM, which I don't anticipate to cause problems to
>> existing code. There are also a few existing documentation pages in drivers or
>> utilities that mention GDAL 2.0 that will need to be changed, but I'll take
>> care of this if the motion is approved (some sed magic should do this).
>>
>> +1 Even
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>>
>>
>> --
>> ---------------------------------------+--------------------------------------
>> I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
>> light and sound - activate the windows | http://pobox.com/~warmerdam
>> and watch the world go round - Rush    | Geospatial Software Developer
>>
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev


More information about the gdal-dev mailing list