[gdal-dev] Understanding GDAL's versioning/release process

[Even Rouault]

On mercredi 5 février 2020 12:20:04 CET Owen Varley wrote:
> Hi all,
> 
> I've been using GDAL for the past couple of months and I have a question
> about how releases are managed that I can't figure out from trawling
> GitHub.
> 
> There's a pull request (#1621) that includes a commit
> (https://github.com/OSGeo/gdal/pull/1621/commits/bcaeb975a703bdec49aff267a1
> a7a8f0c35ab5f2) that was merged into master on 4 Jun 2019. The commit has
> been tagged 3.0.3 and 2.4.4, however, when running gdal v3.0.3 or v3.0.4
> the changes introduced by the commit don't seem to have taken affect.
> Having read through the v3.0.3 release notes
> (https://github.com/OSGeo/gdal/blob/v3.0.3/gdal/NEWS) I can't find any
> mention of #1621 being included.
> 

The way github presents things is indeed confusing... The above mention commit 
is only in master, and certainly not in 2.4.x or 3.0.x tags...

> My question is, if the commit was merged into master on 4 Jun 2019, would it
> not automatically be included within any releases posts that date? If not,
> how do you determine when/if the commit has been released?

git log in the relevant branch/tag and seach for the commit message

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com