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 0476513832E for ; Mon, 15 Aug 2016 16:13:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1F62121C08D; Mon, 15 Aug 2016 16:13:09 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 278DE21C03E for ; Mon, 15 Aug 2016 16:13:07 +0000 (UTC) Received: from localhost (unknown [100.42.103.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: williamh) by smtp.gentoo.org (Postfix) with ESMTPSA id AFE56340F82 for ; Mon, 15 Aug 2016 16:13:06 +0000 (UTC) Date: Mon, 15 Aug 2016 11:12:41 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New Working Group established to evaluate the stable tree Message-ID: <20160815161241.GA21389@whubbs1.gaikai.biz> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <6046d13b-1a54-aa5e-ab16-df448b0f8c59@gentoo.org> <1471248012.31785.32.camel@gentoo.org> <20160815141922.GA3878@linux1.gaikai.biz> <1bff7eb3-cc91-bba7-1f7f-9e7f76906df3@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: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: 14832346-ea0d-4b3c-8be1-ce4cc094f425 X-Archives-Hash: e2e463ab834f3c6b96a9704b3e8bd8f2 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2016 at 04:50:38PM +0200, Kristian Fiskerstrand wrote: > On 08/15/2016 04:49 PM, Kristian Fiskerstrand wrote: > > On 08/15/2016 04:19 PM, William Hubbs wrote: > >> I'm very much for this as well. Themaintainer should be able to > >> stabilize on all arches after the timeout. That would solve the primary > >> concern I have about the stable tree lagging. > >=20 > > It depends on the context, if it is not security related or fixing a > > known bug, it can cause regression for stable users without much gain. > >=20 >=20 > Elaborating on this, if we're talking about maintainer stabilizing it > after testing it properly there is no issue, but there shouldn't be a > policy to auto-mark stable As a maintainer, if there is an old version of a package in stable for some arch and I have a stable request open for a newer version and the arch team doesn't respond to the stable request within a reasonable amount of time, I want to do one of two things: - destabilize all versions of the package on this arch. That would allow me to move on and take the worry about stabilizing this package off of the arch team in the future. or - if there are no blockers, stabilize the new version and deal with the fallout myself if there is any. If there is not an old version of the package marked stable, closing the stablereq and moving on is probably what I would do after a certain amount of time. Maintaining a viable stable tree is a team effort between the maintainers and the arch teams. If the arch teams are so overwhelmed with stable requests that they can't keep things current, the maintainers should be able to stabilize the newer versions and deal with the fallout as a last resort, or decide that they don't want their packages stable on those arches until the arch teams can keep up. William --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlex6fIACgkQblQW9DDEZTgeawCeO+TjRzgALXbP/4iCSvQ7aFig xakAn2RboyclGUVE4DdC7jEiyQxf8edJ =06EX -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--