Hi Javier,
Just a logical consequence of how the release process works. Bug fixes
releases are done from the release/3.9 branch, so the NEWS.md file for a
3.9.x release is edited there, and not in master. And we don't forward
port the changes of the NEWS.md from release/* branches to master. T
On Wed, Jul 17, 2024, at 10:49, Javier Jimenez Shaw wrote:
> I find it strange. There is a long list of news ... but it covers only things
> that were added exactly in the x.y.0 releases. All the changes that happened
> in "bugfix releases" (that is x.y.z for z>0) is only on that branch.
> You
I find it strange. There is a long list of news ... but it covers only
things that were added exactly in the x.y.0 releases. All the changes that
happened in "bugfix releases" (that is x.y.z for z>0) is only on that
branch.
You can compare these two pages
https://github.com/OSGeo/gdal/blob/release/
Try https://github.com/OSGeo/gdal/blob/release/3.9/NEWS.md, I think the patch
release changes either get folded into the next minor changelogs or don't get
included at all. But the release branch always has the full set of changes.
Laurentiu
On Tue, Jul 16, 2024, at 12:09, Javier Jimenez Shaw v
Hi
I noticed that https://github.com/OSGeo/gdal/blob/master/NEWS.md is telling
about 3.9.0, while the last release is 3.9.1
Is that intentional?
Cheers,
Javier
.___ ._ ..._ .. . ._. .___ .. __ . _. . __.. ... ._ .__
___
gdal-dev mailing list
gda
