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