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.43) id 1EC1Mq-0005Eu-AC for garchives@archives.gentoo.org; Sun, 04 Sep 2005 20:45:32 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j84Keodm028907; Sun, 4 Sep 2005 20:40:50 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j84Kbvnn014153 for ; Sun, 4 Sep 2005 20:37:58 GMT Received: from s01060050bab40e5b.ed.shawcable.net ([68.148.132.114] helo=[192.168.0.24]) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1EC1IQ-0007r7-4X for gentoo-dev@lists.gentoo.org; Sun, 04 Sep 2005 20:40:58 +0000 Message-ID: <431B5BC6.50305@gentoo.org> Date: Sun, 04 Sep 2005 14:40:38 -0600 From: Joshua Baergen User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050821) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] tentative x86 arch team glep References: <20050904143711.GD23576@dst.grantgoodyear.org> <20050904194141.4059a55e@snowdrop.home> <20050904191609.GE23576@dst.grantgoodyear.org> <1125864664.11360.107.camel@mogheiden.gnqs.org> In-Reply-To: <1125864664.11360.107.camel@mogheiden.gnqs.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 23f40e0a-6875-4f03-9880-5d967fa82dd1 X-Archives-Hash: b34406877c4d9cd91ed4f2d423aa0caf Stuart Herbert wrote: > >The introduction of the x86 arch >team will, at some point, turn the x86 arch team into a bottleneck (just >like all the other arch teams already are) > > A possible way to alleviate this is proactivity on the maintainer's part. Our current rule for going testing->stable is 30 days. If we could alert the arch teams x number of days in advance they could test it before the end of the period minimizing delays. Since all arch teams would need this alert a relevant script could be created/modified. I realize this doesn't help if the arch teams are just plain too busy. Hopefully the 'fast arch' losing its speed will show people that we need more help in testing and bring more people on board. -- Joshua Baergen -- gentoo-dev@gentoo.org mailing list