On Mon, Jul 14, 2025 at 10:19:43AM +0100, Richard Earnshaw (lists) via Gcc wrote: > On 14/07/2025 08:04, Richard Biener via Gcc wrote: > > On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc <gcc@gcc.gnu.org> > > wrote: > >> > >> Hello Richard, > >> > >> Thank you for making these announcements, they are very useful and > >> informative. But I have one small request to make. Please include a link to > >> the web page that describes the changes from the last release. The links > >> are on the page https://gcc.gnu.org/releases.html and for this particular > >> release, 12.5, the release notes link can be seen from > >> https://gcc.gnu.org/gcc-12 (the changes are at > >> https://gcc.gnu.org/gcc-12/changes.html). > > > > Thanks for the suggestion! I will try to remember this. Note that there > > are usually zero entries in the changes list for minor releases, and I'd > > have to double-check we have a anchor at that sub-section. For new > > major releases we link to the page in the announcements. > > > > A bugzilla scrape for PRs on the release branch might make more sense. But > even that might need curating.
I think for the just closed release branch the bugzilla query at the end of changes.html should be pretty accurate. For other branches the queries contain significantly fewer fixed bugs than actually fixed, because they rely on target milestone, so it provides just lower estimate. Say https://gcc.gnu.org/gcc-14/changes.html#14.3 query then includes only bugs with 14.3 milestone and not ones with say 13.4 or 12.5, even when they are already fixed on the branch. Some of them will be fixed on the older branch too, in other cases it is waiting for (possible) backport. One can also use git and scan say git commit logs between 14.2 and 14.3 tags and extract referenced PRs from there. That provides (almost, with exceptions when people forgot to mention something or mistype) upper estimate on fixed bugs. Or it could be narrowed, take the 14.3 milestone fixed bugs + add to that 13.{4,5} and 12.5 milestone bugs referenced in the git commit logs from 14.2 to 14.3 if they don't have /14 in their summary. Jakub
