| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 12-03-2010 20:47, William Hubbs wrote: |
| 5 |
> On Fri, Mar 12, 2010 at 08:11:50PM +0000, Jeremy Olexa wrote: |
| 6 |
>> |
| 7 |
>> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri R??ty <betelgeuse@g.o> |
| 8 |
>> wrote: |
| 9 |
>>> There seems to be two different schools on who to assign a keywording |
| 10 |
>>> bug with only a single arch. I have myself assigned it to the arch in |
| 11 |
>>> question but there's a difference of opinion here: |
| 12 |
>>> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5 |
| 13 |
>>> Let's get agreed on a single approach and I will add a note here: |
| 14 |
>>> http://devmanual.gentoo.org/keywording/index.html |
| 15 |
>>> I naturally support the approach I have been doing as I think the arch |
| 16 |
>>> team is the one in charge. |
| 17 |
>> |
| 18 |
>> The "problem" with assigning bugs to arch teams is when the user comments |
| 19 |
>> on the bug after it is resolved. If the arch team is CC'd, they remove |
| 20 |
>> themselves when done and any comments after the bug is closed goes to |
| 21 |
>> someone that is interested. If the arch team is assigned, then the comment |
| 22 |
>> basically goes to /dev/null. So, if we are to improve the user experience, |
| 23 |
>> assign to maintainer and CC arch team. |
| 24 |
> |
| 25 |
> This is a good enough reason for me to vote for assigning bugs to |
| 26 |
> maintainers and cc'ing arch teams. This is the way I was taught that |
| 27 |
> this should be handled, and this comment explains why. |
| 28 |
> |
| 29 |
> Since all the arch team does is stabilize or keyword, the maintainer |
| 30 |
> needs to know if other issues come up with the bug after it is closed. |
| 31 |
> |
| 32 |
> William |
| 33 |
|
| 34 |
I agree with the above reasoning, but Petteri raised a good point about |
| 35 |
"old bugs". I suggest that for old bugs we swap the maintainer and the |
| 36 |
arch team so that the maintainer is added to CC and the arch team is |
| 37 |
assigned the bug. If and or when the bug is resolved, the maintainer can |
| 38 |
reassign the bug again. |
| 39 |
|
| 40 |
- -- |
| 41 |
Regards, |
| 42 |
|
| 43 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 44 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v2.0.14 (GNU/Linux) |
| 47 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 48 |
|
| 49 |
iQIcBAEBAgAGBQJLmsb4AAoJEC8ZTXQF1qEPqFAQALJvPNGfW1XGUvNptAIxyWl4 |
| 50 |
5XNRWH4cCgZMgOlESI5DeYRbBySw2ad36CPgm1SLe9AbXtpiDwzNlU4CSZuVZSRZ |
| 51 |
TsQ82/JjWBgYIkRUu81UmzwqGCC8sFwJfKjOGCwrq+bcC0M30GwtGgtRUW9+B8mO |
| 52 |
SdJ56QZdAUiUmHKG9zEW/xiE1U3VThp2Y/PwZP/BsRZqNQK/UpN+m2kPw4lYepGN |
| 53 |
uz9OryVCRXIkIaiPvcX5f94yLCcCtUDQ7JuLuc0tZYQbEKhTPcDtyf0aCfMUIfgr |
| 54 |
dtSulB6N0L4c03aHqpTCc5BeZwKlbh1VSTEBs7izHQ//Cdj3xJPbnmXWPxa5//vW |
| 55 |
p9KLdMl5pYIj/h+ENq7l08nmIsZ0ub7gJZPn2XOF6ywyzKJcX5Pg1oU8jQWdUh3L |
| 56 |
MDUbsZewUz/uubJDG+cawop9hUK0YCazV5DQ8B7niQlR8YNvDBItlsr6yicq4Tkx |
| 57 |
9OFPLXZKC/qG0JTGoOyEYcSdFIHN+4R9SFow8twLnUH5BnMHRS0Qc4Pv1TkaW29Y |
| 58 |
y5Sosf/zt8NWMzBicyXZXnOBSeIhWEobJev2wOgFyFxlp9+HKwzMW4s4iB7ZfKjX |
| 59 |
MAVRGwMjwwqCKUa2usj3BANuIYj8Lb5TKkt1r+2eWysromOIi8J6Z+BTiI/NKdYu |
| 60 |
QB9KakEPzPaiL+/uSrVC |
| 61 |
=OgTi |
| 62 |
-----END PGP SIGNATURE----- |
Archives