From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1H2qJQ-0001ge-Om for garchives@archives.gentoo.org; Fri, 05 Jan 2007 14:44:53 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l05EdGIY026956; Fri, 5 Jan 2007 14:39:16 GMT Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [204.127.225.94]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l05EXU7V032328 for ; Fri, 5 Jan 2007 14:33:30 GMT Received: from [192.168.1.2] (c-24-10-220-25.hsd1.ut.comcast.net[24.10.220.25]) by comcast.net (alnrmhc14) with ESMTP id <20070105143329b1400mk9g6e>; Fri, 5 Jan 2007 14:33:29 +0000 Message-ID: <459E61BB.2060208@gentoo.org> Date: Fri, 05 Jan 2007 07:33:31 -0700 From: Steve Dibb User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.8) Gecko/20061121 SeaMonkey/1.0.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How packages are made stable References: <459D686C.7050304@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 181d2137-64c8-47f9-88b1-c5b877990a78 X-Archives-Hash: 8c25047f670fd959917cfb9816bf9066 Andrey Gerasimenko wrote: > On Fri, 05 Jan 2007 11:49:30 +0300, Robert Cernansky > wrote: > >> On Thu, 04 Jan 2007 13:49:48 -0700 Steve Dibb wrote: >> >>> Andrey Gerasimenko wrote: >>> > Looking at the Portage tree, I see that some packages are kept ~x86 >>> > for long time without any bugs referenced in the changelog or >>> > Bugzilla. How are they being made stable (or where in the docs is the >>> > process described)? >>> They need to be in the tree for at least 30 days, no bugs, and if >>> someone files a stable request ebuild, then an arch tester will test it, >>> and then a dev will keyword it stable. >>> >>> Most stuff doesnt get marked stable mostly because there aren't any >>> stable requests. >> >> Stabilisation bug it not a requirement. Actually, everything I said in that last email was a little off. Stabilization bugs are required because ultimately it is the architecture team that is going to mark it stable, not the developer. There are some cases where things can go directly stable (such as security vulnerabilities), but those are the exception and not the rule. So if you want something stable, do all the checks, file a bug, and copy all the arches that it applies to. You can see which ones use it on http://packages.gentoo.org/ Steve -- gentoo-user@gentoo.org mailing list