[gdal-dev] Motion: Promote GDAL 2.5.0 rc1 for release
Daniel Morissette
dmorissette at mapgears.com
Wed May 1 11:22:37 PDT 2019
I have been wondering about calling it 3.0 as well. How much
communication about 2.5 are you alluding to?
Is it more work to relay that 2.5 had a very short lifespan (i.e. never
released) and then we went straight to 3.0, or to spend the next few
years explaining why 2.4 and 2.5 are not compatible?
On 2019-05-01 13:09, Even Rouault wrote:
> Sean,
>
>>
>> Did you give any more thought to calling this release 3.0 because of the
>> breaking changes? Too late for that?
>
> Yes, that would be a bit annoying to rename it now, at least in terms of
> communication since GDAL 2.5 is already known to be the version with the SRS
> revamp. Would have been more appropriate to raise this at the time RFC 73 was
> discussed.
>
> Re-reading our HOWTO-RELEASE, we should indeed probably have named it GDAL
> 3.0. But even if we add kept the few functions that have been removed, the
> change of behaviour of a few ones is an interesting case of what is considered
> part of the API or not...
>
> Even
>
--
Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201
More information about the gdal-dev
mailing list