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 can compare these two pages > https://github.com/OSGeo/gdal/blob/release/3.8/NEWS.md > https://github.com/OSGeo/gdal/blob/release/3.9/NEWS.md > > However most of the changes are done in master and some back-ported to the > current release branch. That is, if I do a PR in master today that is not > breaking any API, it will be probably backported to 3.9, and released in > 3.9.2. It will appear in the news for 3.9... but it will not appear in the > long list of news for 3.10 and later releases. Right, I thought it would appear in the 3.10 release notes, but you proved it won't.
> Is that what is happening? If yes, do we want to change that? Well, I don't know. It's good to keep the release notes to a reasonable size (otherwise nobody will read them), and the GDAL changelog is pretty large already, but I'll defer to the maintainers on this one. What I can say is that GitHub used to have trouble rendering large Markdown documents, and GDAL is larger than that one already: https://github.com/rust-lang/rust/issues/101714. But it seems fixed now, I suppose they've increased the limit. Still, at some point we'll probably have to split it into NEWS-1.x.md, NEWS-2.x.md etc. Laurentiu > On Tue, 16 Jul 2024 at 11:12, Laurențiu Nicola <lnic...@dend.ro> wrote: >> __ >> 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
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
