]> git.ipfire.org Git - thirdparty/glibc.git/commit
Update advisory format and introduce some automation
authorSiddhesh Poyarekar <siddhesh@sourceware.org>
Wed, 24 Jan 2024 18:37:20 +0000 (13:37 -0500)
committerSiddhesh Poyarekar <siddhesh@sourceware.org>
Tue, 30 Jan 2024 18:58:57 +0000 (13:58 -0500)
commit443c10018cb1e33cd6a054c32eb62881f1dcfca2
tree51298cbb6ed2a8841805c581ff85795efdb37ba0
parent6cdc44214253a74e7140d75a7ebfc900820a5fa8
Update advisory format and introduce some automation

Simplify the advisory format by dropping the -Backport tags and instead
stick to using just the -Commit tags.  To identify backports, put a
substring of git-describe into the release version in the brackets next
to the commit ref.  This way, it not only identifies that the fix (or
regression) is on the release/2.YY/master branch, it also disambiguates
regressions/fixes in the branch from those in the tarball.

Add a README to make it easier for consumers to understand the format.
Additionally, the Release wiki needs to be updated to inform the release
manager to:

1. Generate a NEWS snipped from the advisories directory

AND

2. on release/2.YY/master, replace the advisories directory with a text
   file pointing to the advisories directory in master so that we don't
   have to update multiple locations.

Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Reviewed-by: Andreas K. Hüttel <dilfridge@gentoo.org>
advisories/GLIBC-SA-2023-0001
advisories/GLIBC-SA-2023-0002
advisories/GLIBC-SA-2023-0003
advisories/GLIBC-SA-2023-0004
advisories/GLIBC-SA-2023-0005
advisories/README [new file with mode: 0644]
scripts/process-advisories.sh [new file with mode: 0755]
scripts/process-fixed-cves.sh [deleted file]