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 <gentoo-dev+bounces-41619-garchives=archives.gentoo.org@lists.gentoo.org>) id 1OTD1X-0001w6-MX for garchives@archives.gentoo.org; Mon, 28 Jun 2010 12:01:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AAA3DE0D30; Mon, 28 Jun 2010 12:01:12 +0000 (UTC) Received: from smtp-out.neti.ee (smtp-out.neti.ee [194.126.126.37]) by pigeon.gentoo.org (Postfix) with ESMTP id 8DBCBE0B37 for <gentoo-dev@lists.gentoo.org>; Mon, 28 Jun 2010 12:01:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by relay216.estpak.ee (Postfix) with ESMTP id C7D13DA1 for <gentoo-dev@lists.gentoo.org>; Mon, 28 Jun 2010 15:01:01 +0300 (EEST) X-Virus-Scanned: amavisd-new at estpak.ee Received: from smtp-out.neti.ee ([127.0.0.1]) by localhost (relay216.estpak.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eO5u7xYIlwvm for <gentoo-dev@lists.gentoo.org>; Mon, 28 Jun 2010 15:00:58 +0300 (EEST) Received: from NETI-Relayhost1.estpak.ee (neti-relayhost1.estpak.ee [88.196.174.198]) by relay216.estpak.ee (Postfix) with ESMTP id 753091F21 for <gentoo-dev@lists.gentoo.org>; Mon, 28 Jun 2010 15:00:58 +0300 (EEST) X-SMTP-Auth-NETI-Businessmail: no Subject: Re: [gentoo-dev] Policy for late/slow stabilizations From: Mart Raudsepp <leio@gentoo.org> To: gentoo-dev@lists.gentoo.org In-Reply-To: <201006280949.32308.bangert@gentoo.org> References: <20100627150445.GA19456@Eternity> <AANLkTikQb8eEHSSl6phrTInPSVuQNcSrhBnNjWMM3MNo@mail.gmail.com> <20100627195833.GB2125@Mystical> <201006280949.32308.bangert@gentoo.org> Content-Type: text/plain Date: Mon, 28 Jun 2010 15:01:10 +0300 Message-Id: <1277726470.7368.3.camel@localhost> Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d802fbcf-91b7-4ce4-bee1-877bf01b9f90 X-Archives-Hash: 64356844abe253263760a8210589bf94 On E, 2010-06-28 at 09:49 +0200, Thilo Bangert wrote: > Markos Chandras <hwoarang@gentoo.org> said: > > On Sun, Jun 27, 2010 at 08:15:32PM +0200, Auke Booij wrote: > > > On Sun, Jun 27, 2010 at 7:16 PM, Markos Chandras <hwoarang@gentoo.org> > wrote: > > > > What? I am talking about exotic arches and I didn't say to drop to > > > > entire stable tree. Just to shrink it in order to keep it up to > > > > date more easily > > > > > > But my question stands: what really is the advantage of having a > > > stable tree, when you could better invest your time in keeping the > > > testing tree up to date and working? Most production systems are > > > running x86, right? Are stable versions of minority architecture > > > installations really that much more stable than testing versions? > > > > Because a stable tree it is supposed to work. Testing tree on the other > > hand is vulnerable to breakages from time to time. We can't always > > ensure a working testing tree. We are people not machines. We tend to > > brake things and this is way we have the testing branch. > > also the stable tree implies security support (GLSAs etc). Stable tree does NOT imply security support. I can understand why users might think that, though. A few architectures that have a stable tree are not security supported (GLSAs waiting for them, etc), as can be seen from comparing the arches with stable trees to the security supported architectures list over at http://www.gentoo.org/security/en/vulnerability-policy.xml (at least arm, ia64 and sh by my quick comparison) -- Mart Raudsepp Gentoo Developer Mail: leio@gentoo.org Weblog: http://blogs.gentoo.org/leio