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 A31E7138247 for ; Wed, 15 Jan 2014 00:14:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E42DDE09BF; Wed, 15 Jan 2014 00:14:38 +0000 (UTC) Received: from juliette.telenet-ops.be (juliette.telenet-ops.be [195.130.137.74]) by pigeon.gentoo.org (Postfix) with ESMTP id AEBD3E09A4 for ; Wed, 15 Jan 2014 00:14:37 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by juliette.telenet-ops.be with bizsmtp id E0Ec1n00J2khLEN060EcYS; Wed, 15 Jan 2014 01:14:36 +0100 Date: Wed, 15 Jan 2014 01:13:41 +0100 From: Tom Wijsman To: mjo@gentoo.org Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: revisiting our stabilization policy Message-ID: <20140115011341.6c8395bf@TOMWIJ-GENTOO> In-Reply-To: <52D5BDAD.4030808@gentoo.org> References: <20140114213719.GA2684@laptop.home> <52D5B2CA.5030407@gentoo.org> <20140114223312.GA3337@laptop.home> <52D5BDAD.4030808@gentoo.org> 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: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/nkn35tnj44oN3P1Iz6tS_1k"; protocol="application/pgp-signature" X-Archives-Salt: 1ccaf9a7-a9b1-4d04-bed4-949f899d7a28 X-Archives-Hash: f4d7255f6576afae9f7a31f46c12af0b --Sig_/nkn35tnj44oN3P1Iz6tS_1k Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 14 Jan 2014 17:43:57 -0500 Michael Orlitzky wrote: > It's attempting to fix a headache with a bullet. The arch teams are > lagging behind, you're annoyed, I get it. Give 'em hell. But don't > break stable to make a point. > > For users, both options are worse than the status quo. When you do nothing then things are bound to get worse, under the assumption that manpower doesn't change as well as the assumption that the queue fills faster than stabilization bugs get added to it. As a result of this, stable will eventually become broken. It is up to you as well as us whether to consider it to be broken right now. Will it be in a month from now? What about in a year? Will we wait for hell? Or try to prepare and/or fix it now? Maybe there are other options if these can be deemed as being worse. --=20 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 --Sig_/nkn35tnj44oN3P1Iz6tS_1k Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJS1dK1AAoJEJWyH81tNOV9RBgH/1bOoVcDld0ZDbS7aatdqb/u RKPhAZgLVQmWe8UA132JFXVSy/VH5WTjLh/dTyfhIn4b5ZkvnUBr2So98nNUJtuk dfYR4E8ysH8vFb+lv0ZUATHQjEMWOpzYfxETZl1aGf8RTKfXs9CfOY/4jpl7zNrr MUGWvc2LNxAGt1KAmqE7PWUq4UqA4KI5aCi4oI/hjn8eAoDOVAZoipsny0uo+Prl xRdqno4bu9b+FZMajVn7I6QWaMntZ5UL1h9TXob7n7mvmj9iuE46/qFYxT8gO8im MnMXlfIrMe3srUxmhiRyXrR2PSFTOzh+OVp8wDymPVfcAF0Os+CJyCHSXfXhlT0= =W/pQ -----END PGP SIGNATURE----- --Sig_/nkn35tnj44oN3P1Iz6tS_1k--