[RFC]: Repurpose glibc_X.Y keyword to mean "Fixed in glibc X.Y release branch"

[Carlos O'Donell]

The current purpose of the glic_X.Y keywords is to indicate that a given
bug needs to be backported to glibc_X.Y. My original idea behind this was
that users or distribution maintainers could request certain bugs fixed on
master to be backported to release/X.Y/master via this keyword, and we could
avoid creating a new bug for this request.

Instead of following this process, we have had a better process arise!
We have empowered distro maintainers and vendors to work upstream, backporting
bugs that matter to them (selected from their perspective distro bug
trackers). The distro maintainers are doing a fantastic job of backporting
bugs. Thanks you Aurelien, Florian, Siddhesh, Raji, Arjun, Dmitry, and
many more! This is exactly the way it should work. Need and interest driving
the work.

Therefore nobody uses glibc_X.Y to indicate anything. Developers backport the
bugs themselves, there is no need to mark a bug as needing a backport.
Users of the distros file these bugs in the downstream distro
bug trackers instead of upstream in the glibc bugzilla.

The one thing that is missing from this is an automated way to generate
the bug list on the *release branch* NEWS. We have that automation already
for master via milestone=X.Y, but the milestone UI widget is not multi-select.

I would like to propose we re-purpose the glibc_X.Y tag to indicate
"Fixed in glibc_X.Y", and enhance the list-fixed-bugs.py script to
process keywords in-addition to milestone.

This way the process looks like this:
 
* Commit changes to master, set bug milestone=X.Y.
  * Can update bug list at release with `./list-fixed-bugs.py 2.28`

* Commit changes to release/X.Y-1, set keyword glibc_X.Y-1 in bug.

* Run list-fixed-bugs.py, and commit the changes it generates.
  * Get list of bugs for 2.27.1 with `./list-fixed-bugs.py -b release 2.27`
  * Lists only bugs which were fixed after release e.g. glibc_2.27 keyword and FIXED.

This automates the generation of the list NEWS bug list for release branches.
Users need only cut-and-paste the results before they commit.

Cheers,
Carlos.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fixed-bug-list.patch
Type: text/x-patch
Size: 3963 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20180315/86843b32/attachment.bin>