From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1EGOZy-0006TP-5E for garchives@archives.gentoo.org; Fri, 16 Sep 2005 22:21:10 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j8GMEieZ018552; Fri, 16 Sep 2005 22:14:44 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j8GMBeO0008848 for ; Fri, 16 Sep 2005 22:11:41 GMT Received: from localhost ([127.0.0.1] helo=home.wh0rd.org) by smtp.gentoo.org with esmtp (Exim 4.43) id 1EGOVm-000171-BL for gentoo-dev@lists.gentoo.org; Fri, 16 Sep 2005 22:16:50 +0000 Received: (qmail 10668 invoked from network); 16 Sep 2005 18:12:50 -0400 Received: from unknown (HELO vapier) (192.168.0.2) by 192.168.0.1 with SMTP; 16 Sep 2005 18:12:50 -0400 From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] first council meeting Date: Fri, 16 Sep 2005 18:17:01 -0400 User-Agent: KMail/1.8.2 References: <20050915205149.GB22270@vino.zko.hp.com> <200509161659.56603.vapier@gentoo.org> <1126907853.5006.98.camel@lycan.lan> In-Reply-To: <1126907853.5006.98.camel@lycan.lan> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509161817.01181.vapier@gentoo.org> X-Archives-Salt: 5a4f6a02-b306-48ee-a731-e72e3e8f5fed X-Archives-Hash: f5db3b31e843931b0f63ece660afcfbd On Friday 16 September 2005 05:57 pm, Martin Schlemmer wrote: > On Fri, 2005-09-16 at 16:59 -0400, Mike Frysinger wrote: > > On Friday 16 September 2005 04:44 pm, Ciaran McCreesh wrote: > > > On Fri, 16 Sep 2005 16:33:13 -0400 Mike Frysinger > > > > > > wrote: > > > | ok, e17 packages dont count here. however, your hardcore view i > > > | still dont buy. how about the baselayout-1.9.x -> baselayout-1.11.x > > > | stabilization process ? are you telling me that arch teams should > > > | have had the power to move those into stable without talking to the > > > | maintainer ? baselayout may be a core package, but if you continue > > > | with your hard rule here, then it doesnt matter. > > > > > > I'm saying that arch teams should be allowed to mark it stable if they > > > think it's appropriate. Not that it must be moved to stable after $x > > > days, but that it can be at the arch team's discretion. And any arch > > > team which is silly enough to mark a broken baselayout stable has far > > > bigger problems anyway... > > > > baselayout is an example, any package can be used here (although not many > > are as critical) > > > > i'm saying that the maintainer may have a certain idea of when the > > package is ready for stable (a target feature set, working out certain > > quirks, etc...). your current hard view does not allow for that. for > > example, i had an arch maintainer one time mark bash-3 stable before > > base-system was ready for it (readline, baselayout, etc... were going to > > be stabilized together). i smacked them hard for it, but if we went with > > this hard view, it would have been perfectly acceptable behavior. > > We still have KEYWORDS="-*". Sure, I know many do not like it, and if > something was decided in regards to it, I missed it, but it is generally > seen as 'less severe' than a package.mask'd mask, and its local to the > package, so should not get stale. that would address the 'arch teams marking ahead of maintainer' issue, but in general, i think we need a testing mask of some sort separate from package.mask where we can put things like modular X, new KDE betas, new GNOME betas, e17 packages, etc... -mike -- gentoo-dev@gentoo.org mailing list