This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Bugzilla Procedures
On 02/20/2018 05:48 AM, Joseph Myers wrote:
> On Mon, 19 Feb 2018, Rical Jasan wrote:
>
>> 1) B2 talks about updating NEWS, but NEWS says the fixed-bugs list will
>> be automatically generated at release time.
>
> It needs to refer instead to resolving the bug as FIXED with target
> milestone set, as that's required for the automatic generation.
Updated. [0]
> The references to ports in B1 are also obsolete (but it's still the case
> that it's best to avoid bugs that might be partly fixed by filing multiple
> bugs if in doubt about whether something is one bug or more than one).
Is stripping the ports bits sufficient:
"If in doubt about whether a problem you observe has the same underlying
cause as an existing bug, file a new bug for it rather than adding to
the existing bug; closing duplicate bugs is easier than tracking the
"partly-fixed" state of a bug that has over time changed what issues it
covers."
or should something else be said about opening bugs that (may) affect
multiple components?
Rical
[0] https://sourceware.org/glibc/wiki/Bugzilla%20Procedures