From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JVEdF-0001Vz-4i for garchives@archives.gentoo.org; Fri, 29 Feb 2008 23:27:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C155DE0228; Fri, 29 Feb 2008 23:27:11 +0000 (UTC) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by pigeon.gentoo.org (Postfix) with ESMTP id A8B4CE0228 for ; Fri, 29 Feb 2008 23:27:11 +0000 (UTC) Received: from gw.thefreemanclan.net ([71.242.211.138]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JX0003W9X9DL0E9@vms040.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Fri, 29 Feb 2008 17:29:37 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by gw.thefreemanclan.net (Postfix) with ESMTP id D0C511240CA for ; Fri, 29 Feb 2008 18:26:52 -0500 (EST) Date: Fri, 29 Feb 2008 18:26:52 -0500 From: Richard Freeman Subject: Re: [gentoo-dev] Keyword request interface (SoC candidate?) In-reply-to: <97a7f0880802291127w283962f3jb4c497f36fcf9649@mail.gmail.com> To: gentoo-dev@lists.gentoo.org Message-id: <47C894BC.4050200@gentoo.org> 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=UTF-8; format=flowed Content-transfer-encoding: 7bit References: <3c32af40802280933n1290c88bn35b2b989de29ce1b@mail.gmail.com> <47C772B5.9090905@gentoo.org> <1204278247.6288.22.camel@localhost> <47C7E848.5080009@gentoo.org> <47C84B3C.3080505@gentoo.org> <97a7f0880802291127w283962f3jb4c497f36fcf9649@mail.gmail.com> User-Agent: Thunderbird 2.0.0.9 (X11/20071116) X-Archives-Salt: 0823085a-b734-4aee-a0cd-56cada3b161a X-Archives-Hash: 1a1e4c3fc254a17f701e5a26fa5c974f Aaron Mavrinac wrote: > > This would certainly help coordinate AT efforts. Couldn't this also be > done by searching through bugzilla? Maybe with an "official" keyword, > or some sort of flag we don't otherwise use? (I'm not intensely > familiar with bugzilla internals.) Keeping it all in bugzilla seems > best, if possible. I know that the amd64 team used to use the "STABLE" and "TESTED" keywords to indicate that an AT felt it was ok to keyword stable or ~arch respectively. I guess that practice went away. It doesn't work so well on bugs with 5 archs CC'ed though. Maybe we need STABLEAMD64, STABLEX86, etc. As an AT I used to run queries all the time looking for bugs that weren't keyworded STABLE/TESTED and which otherwise looked like they needed AT attention. I still check the corresponding developer query for stuff keyworded STABLE/TESTED with amd64 CC'ed... There are definitely some easy ways to improve things that don't require code changes... -- gentoo-dev@lists.gentoo.org mailing list