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 8B4CC13832E for ; Mon, 15 Aug 2016 03:54:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 18CA021C08C; Mon, 15 Aug 2016 03:54:15 +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 13788E0BE5 for ; Mon, 15 Aug 2016 03:54:13 +0000 (UTC) Received: from katipo2.lan (unknown [IPv6:2406:e001:1:d01:c2f8:daff:fe83:ed01]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 564E4340A9E for ; Mon, 15 Aug 2016 03:54:12 +0000 (UTC) Date: Mon, 15 Aug 2016 15:53:26 +1200 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New Working Group established to evaluate the stable tree Message-ID: <20160815155326.41c9c33d@katipo2.lan> In-Reply-To: <20160815034522.GB22106@meriadoc.perfinion.com> References: <6046d13b-1a54-aa5e-ab16-df448b0f8c59@gentoo.org> <20160815034522.GB22106@meriadoc.perfinion.com> Organization: Gentoo X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; 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: multipart/signed; micalg=pgp-sha256; boundary="Sig_/yvJ/06XwHxH6n_leajHyWio"; protocol="application/pgp-signature" X-Archives-Salt: 48fa1503-5d09-486a-91af-2e4a09a7c7b0 X-Archives-Hash: dc79d277bb1acdba2811094b0af61fdf --Sig_/yvJ/06XwHxH6n_leajHyWio Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 15 Aug 2016 11:45:22 +0800 Jason Zaman wrote: > IN_PROGRESS =3D=3D we've put the fix in the git repo > RESO/TESTREQ =3D=3D new release and in ~arch TESTREQ was incidentally my first thought. Only needs me to study how much = that's already used and whether or not existing bugs with that flag meet that description or no= t. However, a distinction between IN_PROGRESS and RESO/TESTREQ is not possible= here, because "in git" means "You'll get it if you sync >1h from now" IN_PROGRESS can thus only mean something about it being worked on but not y= et pushed to the main git repo. (ie: overlays, private repos) But I would rather it part of the primary resolution path, not a mere prope= rty of the resolution type. Because its easier to say: UNCONFIRMED -> CONFIRMED -> INPROGRESS -> INVCS -> STABLE Than UNCONFIRMED -> CONFIRMED -> INPROGRESS -> (RESOLVED/TESTREQ) -> (RESOLVED/F= IXED) --Sig_/yvJ/06XwHxH6n_leajHyWio Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXsTzWAAoJEOhUMksTZqggR7IQAKVyuksdL0vvbCyWUtwPfKhY quT3VIwTJRE/hBXVf30j1GtgDsFL02JVKDVLZH5EB8OX5LXNIzNh4KyvOTB3mYhQ sIAyXp2Trm0MNoWidvsVEU+Wb4zjYJg5buvZ71cKnexG2FyMuzTN3nF2hEAdy1kb rzoqelB7eAlxedwz4F3iJ77tQcJlzilzRV6dLLEjY3IDTzBZKXZPjC8f0yOspqas RAeNg1NLIuwWhKnPZc9+tVTzJD3qRCo3hiwsdFe3pmRWIpY2SFCMFLF4YumMIBOR jpUc4AKkct76hnNhq2NkTXczQyz3BFjSnohqPCSHcPCVUjo6wvlaJzuKgvKzCIA+ t8jkooY+cxkH2T8JojKb9sJ6lhtODs5/QoPWE4nP/fau7lHK8XNIPaLNf1Uz4+yv e4V01wgAVYiFQETkG/wH+cj2oSkyFrs1zcgFcVt69J5Kii5e+3up8SHiwHIWFigc a1EIsXsIQSenM8W1dg7bI3BkvOOqimFQMBG306tD222/lqpQ31q4i1rhU64mNCJk FVTu9vcyigO2/jKqwDtge1EWhpY2vmjWYKq8pqWBSSSnDhHsykuqf4z2svRlP/c+ lMY+SXThW0qwNOW209+WaPa4+dQ2OyIdRPHmLa3vFJORRSzudb+mcxh+EEJ+rZhZ FCIM5RbR5cYfsVT+vt0Y =InuO -----END PGP SIGNATURE----- --Sig_/yvJ/06XwHxH6n_leajHyWio--