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 CEA05138BF3 for ; Sun, 16 Feb 2014 18:09:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 519E2E0B28; Sun, 16 Feb 2014 18:09:37 +0000 (UTC) Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 3B1CFE0B0F for ; Sun, 16 Feb 2014 18:09:36 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by andre.telenet-ops.be with bizsmtp id T69b1n00H2khLEN0169bGY; Sun, 16 Feb 2014 19:09:35 +0100 Date: Sun, 16 Feb 2014 19:09:27 +0100 From: Tom Wijsman To: gentoo-dev@lists.gentoo.org Subject: Re: Assigning keyword/stable bugs to arch teams (WAS: [gentoo-dev] dropping redundant stable keywords) Message-ID: <20140216190927.3a6ac06d@TOMWIJ-GENTOO> In-Reply-To: <20140216154623.3fb500a7@marga.jer-c2.orkz.net> 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> <20140215225322.GB1593@laptop.home> <20140216003703.6ceb9116@marga.jer-c2.orkz.net> <1392540063.18051.95.camel@belkin5> <1392560322.18051.129.camel@belkin5> <20140216154623.3fb500a7@marga.jer-c2.orkz.net> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.22; x86_64-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: 8b89739f-fb5a-4d81-8c59-877d51097a07 X-Archives-Hash: d181cb3a031afb0b901af25c1f8991ae On Sun, 16 Feb 2014 15:46:23 +0100 Jeroen Roovers wrote: > > But, I guess there are two major cases: > > - Versions that cannot be stabilized due they not working on that > > arch any longer > > It's probably a good idea to package.mask the affected versions on the > arch profile(s) (with references to bug reports, and so on) so all > users of that profile get to see it. Treat it like a "last rites" > process. Currently that's the only way for users to find out when and > why a package becomes unsupported on a given profile, and it should > work well enough. Give them thirty days to respond or become arch team > members or ATs or just give the nod to an arch developer to say "it > works" - it may even lead to actual stabilisation of a newer ebuild. > > > - Versions that are not stabilized because arch team doesn't have > > the man power to do that. > > As above, package.mask would be a good intermediate solution, > communicating the problem to the arch users for, say, thirty days. Of > course it may just delay solving the problem when a new set of > stabilisations is due and again no one responds. +1, see an example that I wrote earlier at the bottom of this mail: http://article.gmane.org/gmane.linux.gentoo.devel/90083/match=Consider%20this%20instead -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D