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.60) (envelope-from ) id 1GJtRI-0006de-Oj for garchives@archives.gentoo.org; Sun, 03 Sep 2006 14:59:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k83EvXkX018722; Sun, 3 Sep 2006 14:57:33 GMT Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k83Erap3002624 for ; Sun, 3 Sep 2006 14:53:36 GMT Received: from [172.23.170.143] (helo=anti-virus02-10) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1GJtLs-0001qT-Ke for gentoo-dev@lists.gentoo.org; Sun, 03 Sep 2006 15:53:36 +0100 Received: from [82.46.45.60] (helo=gaspode) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1GJtLs-0003PW-5x for gentoo-dev@lists.gentoo.org; Sun, 03 Sep 2006 15:53:36 +0100 Subject: Re: [gentoo-dev] Gentoo 2006.1 From: Christel Dahlskjaer To: gentoo-dev@lists.gentoo.org In-Reply-To: <44FAE883.8090107@gentoo.org> References: <44F95E3E.9000708@gentoo.org> <44F96559.6010003@gentoo.org> <44F96881.90806@gentoo.org> <44F98E43.5040307@gentoo.org> <44FA15D1.2020209@gentoo.org> <44FAE883.8090107@gentoo.org> Content-Type: text/plain Date: Sun, 03 Sep 2006 15:53:36 +0100 Message-Id: <1157295216.6059.68.camel@gaspode> 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 X-Mailer: Evolution 2.6.2 Content-Transfer-Encoding: 7bit X-Archives-Salt: d376e8bd-0b4c-4f0a-b17b-47cbb0f4595a X-Archives-Hash: ded6c1804fa645bba0e4ba2c3fe45516 On Sun, 2006-09-03 at 10:36 -0400, Alec Warner wrote: > Stuart Herbert wrote: > > On 9/3/06, Alec Warner wrote: > >> And no one has implemented any kind of solution. > > > > You need someone to implement a solution? Surely what we need is for > > folks to actually make an announcement in the first place? > > > > I asked for what has become GLEP 42 because we do have a problem > > reaching folks with announcements. But you know what? GLEP 42 > > wouldn't help in cases like this, where there's either no announcement > > at all, or the announcement comes at the last minute. > > > > Technology is just a tool. A technical solution needs something fed > > into it. > > I never specified that the solution had to be technical in nature ;) > > We have the Gentoo Status project, but it's been rather dead lately. We > have PR, but they are more concerned with the release; in the end > GCC-4.1 going stable is up to releng and arch teams (heck it doesn't > technically have to go stable on all arches). So who "screwed up" in > this case? Actually, we spent a fair amount of time talking about Gentoo Status in yesterdays meeting and how to move forwards with that. As for PR, after the Userrel + PR merge we have more manpower, and we're not concerned with just the release. Hell, as far as the release goes, PR for that is done by the Releng team and their PR coordinator. Don't assume that PR isn't interested, but we can't read minds and if people don't keep us in the loop then chances are we miss stuff that could be news worthy. -- gentoo-dev@gentoo.org mailing list