From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PmU5I-0000mh-Au for garchives@archives.gentoo.org; Mon, 07 Feb 2011 16:37:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4B1F11C0C4 for ; Mon, 7 Feb 2011 16:37:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 54F6B1C099 for ; Mon, 7 Feb 2011 16:19:59 +0000 (UTC) Received: from [192.168.1.12] (dvo94.neoplus.adsl.tpnet.pl [83.22.48.94]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id 678551B4062 for ; Mon, 7 Feb 2011 16:19:58 +0000 (UTC) Message-ID: <4D501BA4.6040802@gentoo.org> Date: Mon, 07 Feb 2011 17:19:48 +0100 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 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 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] avoiding urgent stabilizations X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig41AB67F71A93D646D9641809" X-Archives-Salt: X-Archives-Hash: a66142b89250400f17266b3e3c578221 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41AB67F71A93D646D9641809 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =46rom time to time there are stabilization bugs where the current stable= is broken. For example, https://bugs.gentoo.org/show_bug.cgi?id=3D353487 However, in theory that should not happen, because presumably the current stable has been tested in the past and considered not broken. Of course that would be rather idealistic to assume such situation will never happen, but can we do something more to avoid detecting important problems in the stable tree too late? Are we missing something when stabilizing some important packages that later causes the breakages and need for urgent stabilizations? Pawe=C5=82 --------------enig41AB67F71A93D646D9641809 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk1QG6gACgkQuUQtlDBCeQKcVQCfSv1NfOPZGQ1FukGxD0MsJO8H RGkAni3+V8WjWmOncKQwnzI/One3kklK =u2R1 -----END PGP SIGNATURE----- --------------enig41AB67F71A93D646D9641809--