Bugzilla Procedures

Bugzilla Procedures

[Rical Jasan]

The Bugzilla Procedures wiki page [0] looks like it needs some updating.
 I see 2 things that could be fixed after a quick read-through:

1) B2 talks about updating NEWS, but NEWS says the fixed-bugs list will
be automatically generated at release time.

2) A6 looks completely out-of-date.  It has Roland's email in several
components, among others who I'm pretty sure aren't involved any more.

I can update B2, but I think it would take someone with access to
Bugzilla to see who the real auto-CC'd addresses for the various
components are, if we even want to maintain this table anymore.

Thanks,
Rical

Re: Bugzilla Procedures

[Joseph Myers]

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.

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).

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Bugzilla Procedures

[Rical Jasan]

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

Re: Bugzilla Procedures

[Joseph Myers]

On Wed, 21 Feb 2018, Rical Jasan wrote:

> Is stripping the ports bits sufficient:

Yes.

> or should something else be said about opening bugs that (may) affect
> multiple components?

Components in Bugzilla are purely a convenience for classifying and 
finding bugs.  They do not reflect different pieces of code that should be 
committed to separately, if the code related to a bug is spread across 
different parts of glibc.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Bugzilla Procedures

[Carlos O'Donell]

On 02/19/2018 11:45 PM, Rical Jasan wrote:
> The Bugzilla Procedures wiki page [0] looks like it needs some updating.
>  I see 2 things that could be fixed after a quick read-through:
> 
> 1) B2 talks about updating NEWS, but NEWS says the fixed-bugs list will
> be automatically generated at release time.
> 
> 2) A6 looks completely out-of-date.  It has Roland's email in several
> components, among others who I'm pretty sure aren't involved any more.
> 
> I can update B2, but I think it would take someone with access to
> Bugzilla to see who the real auto-CC'd addresses for the various
> components are, if we even want to maintain this table anymore.

I have updated A6. It is easy to keep updated.

You cannot yourself query if you are auto-CC'd, and so the wiki list
serves to show non-admin users which bug components they are auto-CC'd on.

-- 
Cheers,
Carlos.

Re: Bugzilla Procedures

[Rical Jasan]

On 02/21/2018 03:20 PM, Carlos O'Donell wrote:
>> 2) A6 looks completely out-of-date.  It has Roland's email in several
>> components, among others who I'm pretty sure aren't involved any more.
>>
>> I can update B2, but I think it would take someone with access to
>> Bugzilla to see who the real auto-CC'd addresses for the various
>> components are, if we even want to maintain this table anymore.
> I have updated A6. It is easy to keep updated.
> 
> You cannot yourself query if you are auto-CC'd, and so the wiki list
> serves to show non-admin users which bug components they are auto-CC'd on.

Great, thank you!

Rical

Re: Bugzilla Procedures

[Rical Jasan]

On 02/21/2018 09:57 AM, Joseph Myers wrote:
> On Wed, 21 Feb 2018, Rical Jasan wrote:
>> Is stripping the ports bits sufficient:
> Yes.

OK, I updated the page.

Thank you,
Rical