There seems to be two different schools on who to assign a keywording
bug with only a single arch. I have myself assigned it to the arch in
question but there's a difference of opinion here:
http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
Let's get agreed on a single approach and I will add a note here:
http://devmanual.gentoo.org/keywording/index.html
I naturally support the approach I have been doing as I think the arch
team is the one in charge.
Regards,
Petteri
03-12-2010, 06:39 PM
"Paweł Hajdan, Jr."
Handling of keywording bugs with only one arch
On 3/12/10 8:18 PM, Petteri Räty wrote:
> There seems to be two different schools on who to assign a keywording
> bug with only a single arch.
Why a special case for that? The general rule seems to be that the owner
is the maintaining herd (if any), otherwise the maintainer. Then all
arch teams and possible co-maintaining herds are CC-ed.
Anyway, I don't have a strong opinion about any of these, just prefer a
simplicity of the rules.
Paweł Hajdan jr
03-12-2010, 06:54 PM
Samuli Suominen
Handling of keywording bugs with only one arch
On 03/12/2010 09:18 PM, Petteri Räty wrote:
> There seems to be two different schools on who to assign a keywording
> bug with only a single arch. I have myself assigned it to the arch in
> question but there's a difference of opinion here:
> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> Let's get agreed on a single approach and I will add a note here:
> http://devmanual.gentoo.org/keywording/index.html
> I naturally support the approach I have been doing as I think the arch
> team is the one in charge.
>
> Regards,
> Petteri
>
said archteam maintains the _keyword_, not the ebuild maintainers, so
goes to the arch
03-12-2010, 06:55 PM
Petteri Räty
Handling of keywording bugs with only one arch
On 03/12/2010 09:39 PM, "Paweł Hajdan, Jr." wrote:
> On 3/12/10 8:18 PM, Petteri Räty wrote:
>> There seems to be two different schools on who to assign a keywording
>> bug with only a single arch.
>
> Why a special case for that? The general rule seems to be that the owner
> is the maintaining herd (if any), otherwise the maintainer. Then all
> arch teams and possible co-maintaining herds are CC-ed.
>
Perhaps a bad habit but I have been using my way as a gentle reminder on
really old bugs to minor arches that you should do something already by
switching them from Cc to assignee.
Regards,
Petteri
03-12-2010, 07:11 PM
Jeremy Olexa
Handling of keywording bugs with only one arch
On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Räty <betelgeuse@gentoo.org>
wrote:
> There seems to be two different schools on who to assign a keywording
> bug with only a single arch. I have myself assigned it to the arch in
> question but there's a difference of opinion here:
> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> Let's get agreed on a single approach and I will add a note here:
> http://devmanual.gentoo.org/keywording/index.html
> I naturally support the approach I have been doing as I think the arch
> team is the one in charge.
The "problem" with assigning bugs to arch teams is when the user comments
on the bug after it is resolved. If the arch team is CC'd, they remove
themselves when done and any comments after the bug is closed goes to
someone that is interested. If the arch team is assigned, then the comment
basically goes to /dev/null. So, if we are to improve the user experience,
assign to maintainer and CC arch team.
-Jeremy
03-12-2010, 08:47 PM
William Hubbs
Handling of keywording bugs with only one arch
On Fri, Mar 12, 2010 at 08:11:50PM +0000, Jeremy Olexa wrote:
>
> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri R??ty <betelgeuse@gentoo.org>
> wrote:
> > There seems to be two different schools on who to assign a keywording
> > bug with only a single arch. I have myself assigned it to the arch in
> > question but there's a difference of opinion here:
> > http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> > Let's get agreed on a single approach and I will add a note here:
> > http://devmanual.gentoo.org/keywording/index.html
> > I naturally support the approach I have been doing as I think the arch
> > team is the one in charge.
>
> The "problem" with assigning bugs to arch teams is when the user comments
> on the bug after it is resolved. If the arch team is CC'd, they remove
> themselves when done and any comments after the bug is closed goes to
> someone that is interested. If the arch team is assigned, then the comment
> basically goes to /dev/null. So, if we are to improve the user experience,
> assign to maintainer and CC arch team.
This is a good enough reason for me to vote for assigning bugs to
maintainers and cc'ing arch teams. This is the way I was taught that
this should be handled, and this comment explains why.
Since all the arch team does is stabilize or keyword, the maintainer
needs to know if other issues come up with the bug after it is closed.
William
03-12-2010, 09:58 PM
"Jorge Manuel B. S. Vicetto"
Handling of keywording bugs with only one arch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12-03-2010 20:47, William Hubbs wrote:
> On Fri, Mar 12, 2010 at 08:11:50PM +0000, Jeremy Olexa wrote:
>>
>> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri R??ty <betelgeuse@gentoo.org>
>> wrote:
>>> There seems to be two different schools on who to assign a keywording
>>> bug with only a single arch. I have myself assigned it to the arch in
>>> question but there's a difference of opinion here:
>>> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
>>> Let's get agreed on a single approach and I will add a note here:
>>> http://devmanual.gentoo.org/keywording/index.html
>>> I naturally support the approach I have been doing as I think the arch
>>> team is the one in charge.
>>
>> The "problem" with assigning bugs to arch teams is when the user comments
>> on the bug after it is resolved. If the arch team is CC'd, they remove
>> themselves when done and any comments after the bug is closed goes to
>> someone that is interested. If the arch team is assigned, then the comment
>> basically goes to /dev/null. So, if we are to improve the user experience,
>> assign to maintainer and CC arch team.
>
> This is a good enough reason for me to vote for assigning bugs to
> maintainers and cc'ing arch teams. This is the way I was taught that
> this should be handled, and this comment explains why.
>
> Since all the arch team does is stabilize or keyword, the maintainer
> needs to know if other issues come up with the bug after it is closed.
>
> William
I agree with the above reasoning, but Petteri raised a good point about
"old bugs". I suggest that for old bugs we swap the maintainer and the
arch team so that the maintainer is added to CC and the arch team is
assigned the bug. If and or when the bug is resolved, the maintainer can
reassign the bug again.
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
On Fri, 12 Mar 2010 21:18:03 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> There seems to be two different schools on who to assign a keywording
> bug with only a single arch. I have myself assigned it to the arch in
> question but there's a difference of opinion here:
> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> Let's get agreed on a single approach and I will add a note here:
> http://devmanual.gentoo.org/keywording/index.html
> I naturally support the approach I have been doing as I think the arch
> team is the one in charge.
I swear there used to be a piece of documentation that said that the final
arch on a stabilization bug should be assigned and the maintainer moved to
CC. I can't find it any more, but that's probably where this idea came
from. It never really made sense to me but I've done it on several occasions.
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
03-12-2010, 10:17 PM
Matti Bickel
Handling of keywording bugs with only one arch
Ryan Hill wrote:
> I can't find it any more, but that's probably where this idea came
> from. It never really made sense to me but I've done it on several occasions.
me too. I guess it's been handed down for ages.
03-13-2010, 10:08 AM
Markos Chandras
Handling of keywording bugs with only one arch
On Friday 12 March 2010 23:47:05 William Hubbs wrote:
> On Fri, Mar 12, 2010 at 08:11:50PM +0000, Jeremy Olexa wrote:
> > On Fri, 12 Mar 2010 21:18:03 +0200, Petteri R??ty <betelgeuse@gentoo.org>
> >
> > wrote:
> > > There seems to be two different schools on who to assign a keywording
> > > bug with only a single arch. I have myself assigned it to the arch in
> > > question but there's a difference of opinion here:
> > > http://bugs.gentoo.org/show_bug.cgi?id=272160#c5
> > > Let's get agreed on a single approach and I will add a note here:
> > > http://devmanual.gentoo.org/keywording/index.html
> > > I naturally support the approach I have been doing as I think the arch
> > > team is the one in charge.
> >
> > The "problem" with assigning bugs to arch teams is when the user comments
> > on the bug after it is resolved. If the arch team is CC'd, they remove
> > themselves when done and any comments after the bug is closed goes to
> > someone that is interested. If the arch team is assigned, then the
> > comment basically goes to /dev/null. So, if we are to improve the user
> > experience, assign to maintainer and CC arch team.
>
> This is a good enough reason for me to vote for assigning bugs to
> maintainers and cc'ing arch teams. This is the way I was taught that
> this should be handled, and this comment explains why.
>
> Since all the arch team does is stabilize or keyword, the maintainer
> needs to know if other issues come up with the bug after it is closed.
>
> William
I like that idea as well
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Handling of keywording bugs with only one arch
