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 1MpNla-0005nf-Av for garchives@archives.gentoo.org; Sun, 20 Sep 2009 14:51:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B9BBBE06D0; Sun, 20 Sep 2009 14:51:52 +0000 (UTC) Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com [209.85.210.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 9A4E6E06D0 for ; Sun, 20 Sep 2009 14:51:52 +0000 (UTC) Received: by yxe4 with SMTP id 4so2608615yxe.32 for ; Sun, 20 Sep 2009 07:51:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=632+eVULA2A5PR+16RLCbZERjMEVpWSn//GVi0kJo40=; b=V9sBeDUglnWJAmuo+rjqPdxtOFcEqTARBAsux5Wx86xdWRG3r1Kmw/yoM/oqYVQRWH IvPpFdzGHTNVbCHqAbSzew+luFXxtev2aR/hbvJGduQjayqJDUQtd4qI2vPIk6FqXhiM cELenTfQVglPeZQJTqUyVpLeRU1Q4rMBTeICY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=HKsd3Uch49uOKD/HSxFggNwqdnAsPqpcXsyq10x4RtKNJjDSmkwa55Cn8F7vPsyQnk loZTKEz2KXDw9InbIE2n1leK5Ir7gcpmPFBSATCML/nFe3pECCasOL95o+cf3BIqTEHP FT6PeWWip3SalG6WZWmMHjCZ6wofIZcHj1d8o= Received: by 10.90.230.16 with SMTP id c16mr1807570agh.76.1253458312355; Sun, 20 Sep 2009 07:51:52 -0700 (PDT) Received: from ?192.168.1.1? (adsl-144-216-98.jan.bellsouth.net [70.144.216.98]) by mx.google.com with ESMTPS id 39sm6617358agd.68.2009.09.20.07.51.51 (version=SSLv3 cipher=RC4-MD5); Sun, 20 Sep 2009 07:51:51 -0700 (PDT) Message-ID: <4AB64186.3020708@gmail.com> Date: Sun, 20 Sep 2009 09:51:50 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.22) Gecko/20090905 SeaMonkey/1.1.17 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: Re: [gentoo-dev] Stabilization of Python 3.1 References: <200909191848.33225.Arfrever@gentoo.org> <20090919190657.31f109a3@mail.netloc.info> <4AB51317.1000108@gmail.com> <1253381283.31816.9.camel@TesterBox.tester.ca> <4AB60FA3.90903@gentoo.org> In-Reply-To: <4AB60FA3.90903@gentoo.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: bf475a19-6b48-49ea-ba34-5cce5852a600 X-Archives-Hash: b553e53aa1c5d0faa8ada2e2bf4ca42d Richard Freeman wrote: > Olivier Cr=EAte wrote: >> >> ~arch is for testing ebuilds, not the upstream package >> > > I'm pretty sure this isn't the case - at least not as cleanly as you > suggest. Certainly testing the ebuilds themselves is part of the > reason for having ~arch, but upstream readiness is part of it as > well. If a package hit ~arch and we got 10 serious bugs that were all > upstream problems and then somebody filed a STABLEREQ I know that I > wouldn't be the one to stabilize it. > > The whole point of having QA is so that people who don't want to be > bothered with bleeding-edge packages aren't bothered with them.=20 > Masking is for packages with known serious problems, ~arch is for > packages that we think are fine but don't have much production history > with, and stable is for packages that are known to be decent with > history. > > However, I'm not convinced that the 3.1 issues need to be a > showstopper for going stable. Others have made some of these > suggestions, but let me consolidate some ideas that have come up: > > 1. A tracking bug should be created to track 3.1 stabilization issues > (assuming it doesn't already exist). > 2. Portage (and other system packages) deps should be checked to > ensure it pulls in the current version. This should be carefully > coordinated. > 3. -dev-announce message sent out to check your python deps and fix > them (logging blockers as needed). This need not be carefully > coordinated. > 4. einfo message about not eselecting the new version of python.=20 > News message as well. > > As long as the current version doesn't go anywhere and the current > version can be re-selected at-will, then I don't see how users can get > themselves into a corner. > > The ability to support stuff like this is the reason we have SLOTs in > the first place. > > Thanks for explaining that better than I could.=20 Dale :-) :-)=20