Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@g.o>
Subject: Re: Handling of keywording bugs with only one arch
Date: Fri, 12 Mar 2010 21:58:00 -0100
-----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@g.o>
>> 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/

iQIcBAEBAgAGBQJLmsb4AAoJEC8ZTXQF1qEPqFAQALJvPNGfW1XGUvNptAIxyWl4
5XNRWH4cCgZMgOlESI5DeYRbBySw2ad36CPgm1SLe9AbXtpiDwzNlU4CSZuVZSRZ
TsQ82/JjWBgYIkRUu81UmzwqGCC8sFwJfKjOGCwrq+bcC0M30GwtGgtRUW9+B8mO
SdJ56QZdAUiUmHKG9zEW/xiE1U3VThp2Y/PwZP/BsRZqNQK/UpN+m2kPw4lYepGN
uz9OryVCRXIkIaiPvcX5f94yLCcCtUDQ7JuLuc0tZYQbEKhTPcDtyf0aCfMUIfgr
dtSulB6N0L4c03aHqpTCc5BeZwKlbh1VSTEBs7izHQ//Cdj3xJPbnmXWPxa5//vW
p9KLdMl5pYIj/h+ENq7l08nmIsZ0ub7gJZPn2XOF6ywyzKJcX5Pg1oU8jQWdUh3L
MDUbsZewUz/uubJDG+cawop9hUK0YCazV5DQ8B7niQlR8YNvDBItlsr6yicq4Tkx
9OFPLXZKC/qG0JTGoOyEYcSdFIHN+4R9SFow8twLnUH5BnMHRS0Qc4Pv1TkaW29Y
y5Sosf/zt8NWMzBicyXZXnOBSeIhWEobJev2wOgFyFxlp9+HKwzMW4s4iB7ZfKjX
MAVRGwMjwwqCKUa2usj3BANuIYj8Lb5TKkt1r+2eWysromOIi8J6Z+BTiI/NKdYu
QB9KakEPzPaiL+/uSrVC
=OgTi
-----END PGP SIGNATURE-----


References:
Handling of keywording bugs with only one arch
-- Petteri R├Ąty
Re: Handling of keywording bugs with only one arch
-- Jeremy Olexa
Re: Handling of keywording bugs with only one arch
-- William Hubbs
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Handling of keywording bugs with only one arch
Next by thread:
Re: Handling of keywording bugs with only one arch
Previous by date:
Re: Handling of keywording bugs with only one arch
Next by date:
Re: Handling of keywording bugs with only one arch


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.