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