From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32651 invoked by alias); 20 Sep 2009 01:35:44 -0000 Received: (qmail 32643 invoked by uid 22791); 20 Sep 2009 01:35:44 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from ey-out-1920.google.com (HELO ey-out-1920.google.com) (74.125.78.147) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Sep 2009 01:35:41 +0000 Received: by ey-out-1920.google.com with SMTP id 13so439251eye.46 for ; Sat, 19 Sep 2009 18:35:38 -0700 (PDT) Received: by 10.216.73.142 with SMTP id v14mr932275wed.69.1253410538756; Sat, 19 Sep 2009 18:35:38 -0700 (PDT) Received: from ?192.168.2.99? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62]) by mx.google.com with ESMTPS id 7sm3477153eyg.4.2009.09.19.18.35.37 (version=SSLv3 cipher=RC4-MD5); Sat, 19 Sep 2009 18:35:38 -0700 (PDT) Message-ID: <4AB58A42.7030801@gmail.com> Date: Sun, 20 Sep 2009 01:35:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Richard Guenther CC: gcc@gcc.gnu.org Subject: Re: GCC 4.5 Status Report (2009-09-19) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00364.txt.bz2 Richard Guenther wrote: > The trunk is in Stage 1. Stage 1 will end on Sep 30th. After Stage 1 > Stage 3 follows with only bugfixes and no new features allowed. > Stage 3 will end Nov 30th. I don't think this is the best time to do that. Trunk's been broken most of last week and will probably not be buildable for at least several days yet, so a big chunk of that warning period is going to be useless to many people. > We've been accumulating quite a number of P1 bugs. Entering Stage 3 > should allow to improve considerably here in a short time. So aren't we now likely to lose the first few days of what little remains of stage 1 waiting for trunk to start working again, then have a mad rush of people falling all over each other to get their new features in in the last couple of days? One of which will inevitably break trunk again and block all the others and then stage 1 will be over and it'll all be too late? Ten days isn't even that much warning in the first place; it's less time than you'd generally let elapse before pinging a patch. Can I at least raise the suggestion that a plan that might work well would be for us to go slush for however long - less than a week, I'd suppose - it takes us to get trunk really properly stable, and then push back the end of stage 1 by that amount? cheers, DaveK