1 |
On 03/12/2010 09:18 PM, Petteri Räty wrote: |
2 |
> There seems to be two different schools on who to assign a keywording |
3 |
> bug with only a single arch. I have myself assigned it to the arch in |
4 |
> question but there's a difference of opinion here: |
5 |
> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5 |
6 |
> Let's get agreed on a single approach and I will add a note here: |
7 |
> http://devmanual.gentoo.org/keywording/index.html |
8 |
> I naturally support the approach I have been doing as I think the arch |
9 |
> team is the one in charge. |
10 |
> |
11 |
> Regards, |
12 |
> Petteri |
13 |
> |
14 |
|
15 |
So let's summarize for assigning to the single arch: |
16 |
|
17 |
Against (and my comments on why they don't apply): |
18 |
- Comments would only go to arch team after resolving: |
19 |
* maintainer is still in Cc or Reporter |
20 |
- Arch teams not in charge of fixing problems |
21 |
* If problems come up they deserve a new bug as a dependency |
22 |
* one bug per issue and a stabilization bug is about stabilization |
23 |
- Maintainer being able to decide when to go stable |
24 |
* Bug wranglers should still assign to maintainers for their ack |
25 |
* The maintainer assigns it to the arch team |
26 |
|
27 |
In support (and my comments in support): |
28 |
- Can be used as a gentle reminder for slacker arches |
29 |
- The arch teams are actually ones doing the work to resolve the bug |
30 |
* As they are the ones to mark it as resolved it makes sense for them |
31 |
to be the assignees |
32 |
|
33 |
So based on this I propose that I will write this down in appropriate |
34 |
places in to our documentation and commit a week from now. Please object |
35 |
if you don't agree and we can discuss some more. |
36 |
|
37 |
Regards, |
38 |
Petteri |