Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.

[Carlos O'Donell <carlos@redhat.com>]

On 03/15/2018 12:03 PM, Joseph Myers wrote:
> On Thu, 15 Mar 2018, Carlos O'Donell wrote:
> 
>>> +  [22848] ca_ES: update date definitions from CLDR
>>
>> Not marked fixed in 2.28 (target milestone should be set to 2.28 and 
>> marked fixed).
> 
> And people don't seem to be doing a very good job of making the NEWS 
> entries on release branches for fixed bugs look like those on master 
> (which include the name of the component).

All I care about is that the bug is listed, though I agree we could do
a better job.
 
> I advise the approach of using "scripts/list-fixed-bugs.py 2.28" to get 
> the properly formatted entry to add to NEWS on the release branch.  That 
> does of course require you first to have properly marked the bug as fixed 
> with target milestone set.

I could alter the use of the keyword glibc_X.Y to mean "Fixed on branch"
and then alter list-fixed-bugs.py X.Y to search for:

* milestone is X.Y (Bugs fixed in that release, including release branch)

* keywords includes glibc_X.Y (Bugs fixed on the release branch)

This way we avoid the needless creation of new bugs for fixing things
on release branches.

Thoughts?

c.