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 1OSwAa-0004Go-0K for garchives@archives.gentoo.org; Sun, 27 Jun 2010 18:01:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C463FE0CAF; Sun, 27 Jun 2010 18:01:22 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 2B383E0CA3 for ; Sun, 27 Jun 2010 18:01:07 +0000 (UTC) Received: by wwb17 with SMTP id 17so2313813wwb.40 for ; Sun, 27 Jun 2010 11:01:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=tgQWzCCe2qvRI/e2j5q+BrF/YB1RJYVrNCfOVnE7T5w=; b=uLPPkj3vgjGkK8UnUMcIEJig2S8wWYAsNt/2BfkPlDHuvLjWMbhTe3vVvxYAITH+g4 LeW9XzTdnyWpAmRcEze9xmpy40zccM22DEeeGfdS2Cs0Unj8w1pS8hUnh9gEfBT0Jcq8 3giJmrizvsuJMOAHJLTkEXmjlhSptv3iBOGks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=h14+ywT9/V//kSifqEJfLE9mQbPDYyckk6oRYugSkE26YMYJG51QVP8FNkcYz7gk6M evt1wZu9L0GxzggDY4fq7wHVpVkgPP81SpnEn/6u2IapreY72WQSVC2TbLQYXcOMBp/r UhAEL7snhveJU1HPwl+AboudMS4Ec9+bFXLWA= Received: by 10.216.93.2 with SMTP id k2mr2786613wef.56.1277661666497; Sun, 27 Jun 2010 11:01:06 -0700 (PDT) Received: from Blade (kerberos.silverarrow.org [109.74.206.189]) by mx.google.com with ESMTPS id u81sm2338259wei.4.2010.06.27.11.01.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 27 Jun 2010 11:01:06 -0700 (PDT) Sender: Markos Chandras Date: Sun, 27 Jun 2010 19:01:13 +0100 From: Markos Chandras To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Policy for late/slow stabilizations Message-ID: <20100627180113.GA12949@Blade> References: <20100627150445.GA19456@Eternity> <20100627173834.230f0f76@snowcone> <20100627172233.GB1414@Mystical> <20100627184330.4888ce8a@snowcone> 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="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20100627184330.4888ce8a@snowcone> User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: 17309b97-6d79-47a4-b2cf-1ccc1a991926 X-Archives-Hash: 037aaf96dcdcbd7fa4ce4d04541d2103 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 27, 2010 at 06:43:30PM +0100, Ciaran McCreesh wrote: >=20 > Which is the decision to make: make things very difficult for minority > arch users, who get screwed over royally every time keywords are > dropped, or make things slightly more inconvenient for developers, who > have to keep some things around for longer. It's all down to whether > you think happy users are more important than happy developers. >=20 > --=20 > Ciaran McCreesh Please explain me why keeping foobar-1.0 ( Released in 10/12/2009 ) is in favor of a ppc64 stable user when amd64/x86 has foobar-2.1.3 ( Released 60 days ago ) already stabled for them What if a foobar-1.0 bug pops up? What kind of support will that user get from the gentoo or upstream maintainer. The most frequent answer would be "Please update to 2.1.3. 1.0 is 0ld". Yes, not droppping the keywords is convenient for users but in this case their stable tree gets obsolet and unsupported --=20 Markos Chandras (hwoarang) Gentoo Linux Developer Web: http://hwoarang.silverarrow.org --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkwnkekACgkQ9/cejkQaxBCzKACbBHTVzbXOc9CrqKNNP2uTPi1v uQkAn17eVxGPNVTWKyNfXe/9i4jXRPSA =r6A+ -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--