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 01C6F1381F3 for ; Mon, 27 May 2013 10:54:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A66A8E0B2A; Mon, 27 May 2013 10:54:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BB963E0B18 for ; Mon, 27 May 2013 10:54:40 +0000 (UTC) Received: from marga.jer-c2.orkz.net (D4B2706A.static.ziggozakelijk.nl [212.178.112.106]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jer) by smtp.gentoo.org (Postfix) with ESMTPSA id 50D3C33E0A8 for ; Mon, 27 May 2013 10:54:39 +0000 (UTC) Date: Mon, 27 May 2013 12:54:33 +0200 From: Jeroen Roovers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: robo-stable bugs Message-ID: <20130527125433.01b758c9@marga.jer-c2.orkz.net> In-Reply-To: <20130523234042.26eaac89@caribou.gateway.2wire.net> References: <20130519154027.37b6cdf4@marga.jer-c2.orkz.net> <20130521185720.2d63368a@caribou.gateway.2wire.net> <20130522105826.69a27217@TOMWIJ-GENTOO> <20130523234042.26eaac89@caribou.gateway.2wire.net> X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.17; i686-pc-linux-gnu) 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: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: a73ef499-fb61-410b-bf71-28562fba8651 X-Archives-Hash: 8c485b8022755a27a758f0e78cf81909 On Thu, 23 May 2013 23:40:42 -0600 Ryan Hill wrote: > Okay, so what are you using the STABLEREQ keyword for that you want > to set it when the bug is filed but before archs are added? If you > want to see only stabilization bugs you can search in the Keywording > and Stabilization component. Can you suggest another way to search > for stabilization bugs that don't yet have archs CC'd (which is > something I find rather useful)? We could split up [Keywording and Stabilization] into separate components, [Keywording] and [Stabilization], but then 1) people would still forget to set it, at whatever stage, and 2) this wouldn't fit with [Security]/[Vulnerabilities]. It's important to be able to distinguish between STABLEREQ and KEYWORDREQ. I think a KEYWORDREQ should normally be handled earlier than any STABLEREQ /unless/ the STABLEREQ fixes a security bug, since being late getting keywords back up to par with other architectures tends to make an even bigger mess further on. Alternatively, we could set CONFIRMED or IN_PROGRESS when a) the Component is [Keywording and Stabilization] and b) arch teams are CC'd, but then everyone would forget to set that half the time, too. jer