FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 03-12-2010, 06:18 PM
Petteri Rty
 
Default Handling of keywording bugs with only one arch

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
 
Old 03-12-2010, 06:39 PM
"Paweł Hajdan, Jr."
 
Default 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
 
Old 03-12-2010, 06:54 PM
Samuli Suominen
 
Default Handling of keywording bugs with only one arch

On 03/12/2010 09:18 PM, Petteri Rty 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
 
Old 03-12-2010, 06:55 PM
Petteri Räty
 
Default 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
 
Old 03-12-2010, 07:11 PM
Jeremy Olexa
 
Default Handling of keywording bugs with only one arch

On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Rty <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
 
Old 03-12-2010, 08:47 PM
William Hubbs
 
Default 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
 
Old 03-12-2010, 09:58 PM
"Jorge Manuel B. S. Vicetto"
 
Default 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/

iQIcBAEBAgAGBQJLmsb4AAoJEC8ZTXQF1qEPqFAQALJvPNGfW1 XGUvNptAIxyWl4
5XNRWH4cCgZMgOlESI5DeYRbBySw2ad36CPgm1SLe9AbXtpiDw zNlU4CSZuVZSRZ
TsQ82/JjWBgYIkRUu81UmzwqGCC8sFwJfKjOGCwrq+bcC0M30GwtGgtR UW9+B8mO
SdJ56QZdAUiUmHKG9zEW/xiE1U3VThp2Y/PwZP/BsRZqNQK/UpN+m2kPw4lYepGN
uz9OryVCRXIkIaiPvcX5f94yLCcCtUDQ7JuLuc0tZYQbEKhTPc Dtyf0aCfMUIfgr
dtSulB6N0L4c03aHqpTCc5BeZwKlbh1VSTEBs7izHQ//Cdj3xJPbnmXWPxa5//vW
p9KLdMl5pYIj/h+ENq7l08nmIsZ0ub7gJZPn2XOF6ywyzKJcX5Pg1oU8jQWdUh3 L
MDUbsZewUz/uubJDG+cawop9hUK0YCazV5DQ8B7niQlR8YNvDBItlsr6yicq4 Tkx
9OFPLXZKC/qG0JTGoOyEYcSdFIHN+4R9SFow8twLnUH5BnMHRS0Qc4Pv1Tka W29Y
y5Sosf/zt8NWMzBicyXZXnOBSeIhWEobJev2wOgFyFxlp9+HKwzMW4s4i B7ZfKjX
MAVRGwMjwwqCKUa2usj3BANuIYj8Lb5TKkt1r+2eWysromOIi8 J6Z+BTiI/NKdYu
QB9KakEPzPaiL+/uSrVC
=OgTi
-----END PGP SIGNATURE-----
 
Old 03-12-2010, 10:03 PM
Ryan Hill
 
Default Handling of keywording bugs with only one arch

On Fri, 12 Mar 2010 21:18:03 +0200
Petteri Rty <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
 
Old 03-12-2010, 10:17 PM
Matti Bickel
 
Default 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.
 
Old 03-13-2010, 10:08 AM
Markos Chandras
 
Default 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
 

Thread Tools




All times are GMT. The time now is 08:40 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org