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

[jratike80]

Hi,

Master or "trunk" is the development branch. Current trunk will be released
as GDAL 3.1 perhaps around May 2020. New features are developed into trunk
but some changes, mainly bug fixes and especially bug fixes which deal with
security issues, are also backported into one of more released branches.

You are referring to a pull request that adds a new driver for creating
cloud optimized GeoTIFFs. Such large contributions which add new
functionalities are not backported. It is also documented in the driver page
https://gdal.org/drivers/raster/cog.html#raster-cog "New in version 3.1". If
you want to use the COG driver before that you must compile GDAL from the
master or if you are a Windows users you can download compiled binaries from
OSGeo4W or from gisinternals.com.

-Jukka Rahkonen-



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/bcaeb975a703bdec49aff267a1a7a8f0c35ab5f2)
> 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.
> 
> 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?
> 
> Many thanks,
> 
> Owen
> [http://revolutionindefence.com/images/logobanner.png]
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. If you are
> not the intended recipient of this email, you must neither take any action
> based upon its contents, nor copy or show it to anyone. Please contact the
> sender if you believe you have received this email in error. Inzpire
> retains personal data relating to our customers and partners for the
> purposes of conducting a business relationship, communicating and
> marketing to them as well as to providing invitations to upcoming events.
> Please see our Privacy Notice
> <https://www.inzpire.com/privacy-cookie-policy/> for further
> information. In accordance with our Privacy Notice, you have the right to
> withdraw your consent at any time. Inzpire may monitor email traffic data
> and also the content of email for the purposes of security. Inzpire
> Limited (Registered in England & Wales: Company Number: 05456427)
> Registered office: Unit 1B, Alpha Court Business Park, Kingsley Road,
> Lincoln, LN6 3TA. https://www.inzpire.com
> 
> _______________________________________________
> gdal-dev mailing list

> gdal-dev at .osgeo

> https://lists.osgeo.org/mailman/listinfo/gdal-dev





--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html