From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9CDD113832E for ; Tue, 16 Aug 2016 13:52:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 99A9521C1A6; Tue, 16 Aug 2016 13:52:46 +0000 (UTC) Received: from mail-oi0-f67.google.com (mail-oi0-f67.google.com [209.85.218.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9A5EF21C0A3 for ; Tue, 16 Aug 2016 13:52:45 +0000 (UTC) Received: by mail-oi0-f67.google.com with SMTP id e80so6916212oig.2 for ; Tue, 16 Aug 2016 06:52:45 -0700 (PDT) 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-disposition:in-reply-to:user-agent; bh=SDlQgSQVge6YJsNrfMo8UI15iYN35qPiz+7G06F2KXY=; b=wJfAOEYwIAaFA/PoSmFr5bkooD5nkIl5xVaBQJ9PHicdIb3IY+v9lyxVQZtao2ENSt LWFTljptPJWEKo1gZCt//weZ6ORhzPnJ2VfCDRN230aWsrLCHHbamta69P9lOFpTKUUl nBLUWwPAQc4VIMOzMlf6BZSJidFneRy1Iz925SmbPWDZh5P4/T6RRfOxRVJ/Ij6Igkm8 Ezy9eKDHBHzlVk4xIn+kJeGEzZlTKusW9ZQIYIbLbThd35M/TrhUW0ioiSB7SFHdD1w8 auMPRpUxZT0oZnAFhIvtXg3IEt77juWNpWeuQltsr7NmDsXXB0JKsuB7R+bGUF8eSl+e wN5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=SDlQgSQVge6YJsNrfMo8UI15iYN35qPiz+7G06F2KXY=; b=H7KX51ahBvJRrlVPAiWLyphHawbHinMmAro9yB+n+Qp0xUt3w8K+wmRK4nGpgA2kJv K5QJNH4qCG/222z6dqkc42LmRyTnx6nLjDzfdb3Dt3LLY/x+vIpZNE6HfjRBxZzRqA4h rSB/e8drmbCX+gVwUax3BoN+RobR1xFtjrLcG3eA9+0cRRs1f23yO+6LdINS3sXFtV8o foOctLQmNnXYUANnQAPyd7EIN/aBJWK4KYprbEryz0Hfw2JdKN2qU3tRxkUTke0RMWxO zIFgC36v0MSfczxfmIrB8Ei1nr5Yi15k3Z9dc5fWy1LRVUy8e13mzjdQ5I8NhpqZD1A8 EOOQ== X-Gm-Message-State: AEkoousbfaN+X520VRWV49G51dlB0pQH6I79JkrY5GKDnyUGTBZkxR4YGSCCjvDtQ1WRjQ== X-Received: by 10.157.32.46 with SMTP id n43mr16919071ota.120.1471355564507; Tue, 16 Aug 2016 06:52:44 -0700 (PDT) Received: from linux1 (cpe-66-68-34-247.austin.res.rr.com. [66.68.34.247]) by smtp.gmail.com with ESMTPSA id 73sm12554497otg.35.2016.08.16.06.52.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Aug 2016 06:52:43 -0700 (PDT) Sender: William Hubbs Received: (nullmailer pid 18611 invoked by uid 1000); Tue, 16 Aug 2016 13:52:34 -0000 Date: Tue, 16 Aug 2016 08:52:34 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: New Working Group established to evaluate the stable tree Message-ID: <20160816135234.GA18485@linux1.gaikai.biz> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20160815141922.GA3878@linux1.gaikai.biz> <1bff7eb3-cc91-bba7-1f7f-9e7f76906df3@gentoo.org> <20160815161241.GA21389@whubbs1.gaikai.biz> <20160815173130.GA21750@whubbs1.gaikai.biz> <20160815191248.GA21981@whubbs1.gaikai.biz> <20160815200105.GA22318@whubbs1.gaikai.biz> 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="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: 7ec3eede-4021-41f6-9fd8-f85d3cc1519c X-Archives-Hash: a205f82d446f94de754248b10b78969b --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 16, 2016 at 08:02:29AM +0000, Duncan wrote: > William Hubbs posted on Mon, 15 Aug 2016 15:01:05 -0500 as excerpted: >=20 > > =20 > > This works unless you are talking about packages in @system. > > I do see core packages on these arches also languish in ~ for months > > with open stable requests. > >=20 > > The only way to handle one of those would be to remove the old version > > and let their deptree break until they catch up. >=20 > If system-core packages are languishing in ~ for months on some archs,=20 > isn't it time for maintainers of those system packages to appeal to=20 > council to regress those archs to experimental and kill their stable=20 > keywords "at will"? A decision like this doesn['t actually have to involve the council. There's nothing stopping an arch team, right now, from changing their profile to dev or exp. Also, from where I sit personally, arch teams can do several things with keywordreqs and stablereqs they don't do usually. For keywordreqs, they could just not keyword the package and say that they don't feel they have enough resources to support it. For stablereqs, they aren't required to stabilize, but if they choose not to stabilize the new version, I feel they should destabilize all older versions as well so that maintainers can remove them. There's not a requirement that arch teams support every package that comes to them, even if they want their profiles to have stable status. If an architecture has stable status, I would say that the @system set and = all of its reverse dependencies should be kept stable, but everything else is optional, depending on manpower etc. William --AhhlLboLdkugWU4S Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlezGp4ACgkQblQW9DDEZTi1vwCZAaNwjaFM/W/HbGHKyAG2KGSS x4gAnjJGTbmCkHyJYyyuwKCzxlN40lBn =RL6K -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--