1 |
On Sat, 27 Mar 2010 16:26:46 +0200 |
2 |
Petteri Räty <betelgeuse@g.o> wrote: |
3 |
|
4 |
> On 03/12/2010 09:18 PM, Petteri Räty wrote: |
5 |
> > There seems to be two different schools on who to assign a keywording |
6 |
> > bug with only a single arch. I have myself assigned it to the arch in |
7 |
> > question but there's a difference of opinion here: |
8 |
> > http://bugs.gentoo.org/show_bug.cgi?id=272160#c5 |
9 |
> > Let's get agreed on a single approach and I will add a note here: |
10 |
> > http://devmanual.gentoo.org/keywording/index.html |
11 |
> > I naturally support the approach I have been doing as I think the arch |
12 |
> > team is the one in charge. |
13 |
> > |
14 |
> > Regards, |
15 |
> > Petteri |
16 |
> > |
17 |
> |
18 |
> So let's summarize for assigning to the single arch: |
19 |
> |
20 |
> Against (and my comments on why they don't apply): |
21 |
> - Comments would only go to arch team after resolving: |
22 |
> * maintainer is still in Cc or Reporter |
23 |
> - Arch teams not in charge of fixing problems |
24 |
> * If problems come up they deserve a new bug as a dependency |
25 |
> * one bug per issue and a stabilization bug is about stabilization |
26 |
> - Maintainer being able to decide when to go stable |
27 |
> * Bug wranglers should still assign to maintainers for their ack |
28 |
> * The maintainer assigns it to the arch team |
29 |
> |
30 |
> In support (and my comments in support): |
31 |
> - Can be used as a gentle reminder for slacker arches |
32 |
> - The arch teams are actually ones doing the work to resolve the bug |
33 |
> * As they are the ones to mark it as resolved it makes sense for them |
34 |
> to be the assignees |
35 |
> |
36 |
> So based on this I propose that I will write this down in appropriate |
37 |
> places in to our documentation and commit a week from now. Please object |
38 |
> if you don't agree and we can discuss some more. |
39 |
|
40 |
You ignored my point about this being completely moot once we start using |
41 |
flags in bugzilla for arch teams. We'll have to change the policy then |
42 |
to the maintainer being the assignee anyways. |
43 |
|
44 |
|
45 |
-- |
46 |
fonts, by design, by neglect |
47 |
gcc-porting, for a fact or just for effect |
48 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |