From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D030C138BF3 for ; Sat, 15 Feb 2014 22:53:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 19541E0A7C; Sat, 15 Feb 2014 22:53:05 +0000 (UTC) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0CB84E09A9 for ; Sat, 15 Feb 2014 22:53:03 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id vb8so15590756obc.3 for ; Sat, 15 Feb 2014 14:53:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=uZ55YhXYho3kumf4GY2dEgb+V6c9zNsKRqcPwBZb+yQ=; b=xynIO5k2bLMTxDkWXZnGV/idxVfViyfrxKmn2MGzZQ7DZYeLZJgd+5gszhOPVUZtOY 5MOFlkpTsqUpfnCe6o6XK41hpv/KOhg112Uj1PWA4pmpkpt60oHlv7Ivr5bt/f9M6hiP jQrfeLmkx8tZqrKKoUJtBWHlheF+YoE667N9EyiijcKK/atJX/oAQQu1rLP2g6fwBko+ biYKvYlo4AH1Nydbnt8zxX1eMQ8jlSNPxLXEbJVWc9tTSx5ndbLRrr/zi4L+oFnNbsZe WhdkBpAZHQO3RIAanHRStsAoOE8hYR4PmAtQutVXSbVcxBUxwiA+3DLjfWD00OFMKu1n 1RwQ== X-Received: by 10.60.93.102 with SMTP id ct6mr13619991oeb.12.1392504783328; Sat, 15 Feb 2014 14:53:03 -0800 (PST) Received: from laptop (cpe-76-187-91-128.tx.res.rr.com. [76.187.91.128]) by mx.google.com with ESMTPSA id bx1sm69123239oec.8.2014.02.15.14.53.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Feb 2014 14:53:02 -0800 (PST) Sender: William Hubbs Received: by laptop (sSMTP sendmail emulation); Sat, 15 Feb 2014 16:53:22 -0600 Date: Sat, 15 Feb 2014 16:53:22 -0600 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: Assigning keyword/stable bugs to arch teams (WAS: [gentoo-dev] dropping redundant stable keywords) Message-ID: <20140215225322.GB1593@laptop.home> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20140128182304.7d458a17@marga.jer-c2.orkz.net> <20140203062524.GA7467@rathaus.eclipse.co.uk> <20140203104341.2add2760@TOMWIJ-GENTOO> <20140204210319.GA1935@rathaus.eclipse.co.uk> <20140205010833.1bcf8dca@TOMWIJ-GENTOO> <20140213212818.GA2199@rathaus.eclipse.co.uk> <20140214195958.5aea85f0@TOMWIJ-GENTOO> <20140215012855.417f1caa@marga.jer-c2.orkz.net> <20140215114157.6abe3da5@TOMWIJ-GENTOO> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pd0ReVV5GZGQvF3a" Content-Disposition: inline In-Reply-To: <20140215114157.6abe3da5@TOMWIJ-GENTOO> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 20d27f7b-8c57-445f-88a4-84a9c752e9a6 X-Archives-Hash: ecda256dc63f8c9eb62711c99665f688 --Pd0ReVV5GZGQvF3a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 15, 2014 at 11:41:57AM +0100, Tom Wijsman wrote: > On Sat, 15 Feb 2014 01:28:55 +0100 > Jeroen Roovers wrote: >=20 > > On Fri, 14 Feb 2014 19:59:58 +0100 > > Tom Wijsman wrote: > >=20 > > > > And that can work without a problem if we have a mechanism > > > > in place to relieve maintainers of those bugs. > > >=20 > > > 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. > >=20 > > Assigning bugs so arch teams is cosmetic at best. >=20 > 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. The problem with this is, what if it is more than one arch team? Which one do you assign it to? If we want a separate assignee for old stabilizations, what about a separate project that handles this, or maybe we could assign the bugs to m-n or something until the arch teams catch up? William --Pd0ReVV5GZGQvF3a Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL/7+IACgkQblQW9DDEZThlbQCgmtX9kMVxjqdXuXa1hOpAcxfp uwIAoLZE9nRh0OTovFG8UtWdSjDUIbZI =D+dj -----END PGP SIGNATURE----- --Pd0ReVV5GZGQvF3a--