| 1 |
On Sat, 15 Feb 2014 01:28:55 +0100 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
|
| 4 |
> On Fri, 14 Feb 2014 19:59:58 +0100 |
| 5 |
> Tom Wijsman <TomWij@g.o> wrote: |
| 6 |
> |
| 7 |
> > > And that can work without a problem if we have a mechanism |
| 8 |
> > > in place to relieve maintainers of those bugs. |
| 9 |
> > |
| 10 |
> > Such mechanism could be to assign those bug to the arch team, this |
| 11 |
> > idea came up at FOSDEM; it won't solve the lack of manpower, but it |
| 12 |
> > will at least relieve the maintainers and make the problem more |
| 13 |
> > visible. |
| 14 |
> |
| 15 |
> Assigning bugs so arch teams is cosmetic at best. |
| 16 |
|
| 17 |
While it was not explained here, the idea can also move the actual |
| 18 |
maintenance of the ebuild to the arch team; such that it becomes the |
| 19 |
arch team's responsibility to deal with it, or rather don't deal with |
| 20 |
it and have it act as a nagging reminder that stabilization really is |
| 21 |
due. This also reflects the importance of the package, as it will |
| 22 |
receive more attention and thus be more verbose towards the arch team. |
| 23 |
|
| 24 |
> Also note that it used to be that way long ago, and it didn't do any |
| 25 |
> good for anyone involved. |
| 26 |
|
| 27 |
Did it involve a shift in maintenance back then? |
| 28 |
|
| 29 |
> It really doesn't matter who is assigned a bug report, as long as |
| 30 |
> it's not a (theoretically) transiently involved party like an arch |
| 31 |
> team on a stabilisation bug. |
| 32 |
> |
| 33 |
> Recently I've seen a few keywording/stabilisation bug reports assigned |
| 34 |
> to arch teams again. It's really annoying. If you've started doing |
| 35 |
> this, then please stop before people start to think it's a good idea. |
| 36 |
> It's not. |
| 37 |
|
| 38 |
Depends on what the arch teams think of this; but considering that |
| 39 |
these are old ebuilds are the responsibility of the arch team (as they |
| 40 |
keep them in place), you should note that they will eventually cause |
| 41 |
the arch team to get contacted about those bus anyway in one way or |
| 42 |
another sooner or later. Not doing this myself; but I think that people |
| 43 |
might have started doing this, after seeing it pass by after FOSDEM on |
| 44 |
the #gentoo-dev IRC channel (or because they consider it common sense). |
| 45 |
|
| 46 |
Thank you for your opinion on this (as you are an arch team member). |
| 47 |
|
| 48 |
-- |
| 49 |
With kind regards, |
| 50 |
|
| 51 |
Tom Wijsman (TomWij) |
| 52 |
Gentoo Developer |
| 53 |
|
| 54 |
E-mail address : TomWij@g.o |
| 55 |
GPG Public Key : 6D34E57D |
| 56 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives