From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4390 invoked by alias); 31 Jan 2003 00:30:43 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 4383 invoked from network); 31 Jan 2003 00:30:42 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by 172.16.49.205 with SMTP; 31 Jan 2003 00:30:42 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h0V0Tkjj019535; Fri, 31 Jan 2003 01:29:46 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h0V0Tk6s019534; Fri, 31 Jan 2003 01:29:46 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Benjamin Kosnik Cc: gcc@gcc.gnu.org, mark@codesourcery.com Subject: Re: GCC 3.3, GCC 3.4 References: <20030130181313.7d3c5820.bkoz@redhat.com> From: Gabriel Dos Reis In-Reply-To: <20030130181313.7d3c5820.bkoz@redhat.com> Organization: Integrable Solutions Date: Fri, 31 Jan 2003 01:14:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-01/txt/msg01705.txt.bz2 Benjamin Kosnik writes: | >Feel free to suggest a better one! | | Perhaps updating this would help this discussion: | http://gcc.gnu.org/develop.html#future | | Shipping GCC 3.3.0 on March 1 will require enormous effort. | | I guess I'm more concerned about the timing on the gcc-3.4.0 effort. | >From the above link, I cannot tell when it's supposed to be released. | | Anyway. I guess I'm just really leery of releases a la 3.1.0. That | release was pushed back into the summer, when students are out of | school, people are on vacation, etc. I would suggest we really make major releases at most twice in the year (I don't believe there is any point in trying to make the highest number of major releases) but make dot or bug fix releases every two months. [...] | I've versioned the runtimes assuming that 3.3 will not break the 3.2 | ABI, and that 3.4 will. Lacking clear guidance on what to do, I think | this was an ok decision. | | I'd prefer a better process though. Agreed. -- Gaby