From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23644 invoked by alias); 26 Mar 2002 22:37:21 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23565 invoked from network); 26 Mar 2002 22:37:16 -0000 Received: from unknown (HELO igw3.watson.ibm.com) (198.81.209.18) by sources.redhat.com with SMTP; 26 Mar 2002 22:37:16 -0000 Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com [9.2.112.57]) by igw3.watson.ibm.com (8.11.4/8.11.4) with ESMTP id g2QMaXG12996; Tue, 26 Mar 2002 17:36:33 -0500 Received: from makai.watson.ibm.com (makai.watson.ibm.com [9.2.216.144]) by sp1n293en1.watson.ibm.com (8.11.4/8.11.4) with ESMTP id g2QMaXO27234; Tue, 26 Mar 2002 17:36:33 -0500 Received: from watson.ibm.com (localhost [127.0.0.1]) by makai.watson.ibm.com (AIX4.3/8.9.3/8.9.3/01-10-2000) with ESMTP id RAA26398; Tue, 26 Mar 2002 17:36:32 -0500 Message-Id: <200203262236.RAA26398@makai.watson.ibm.com> To: Richard Henderson , Zack Weinberg , Jim Blandy , gcc@gcc.gnu.org, gdb@sources.redhat.com Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC] In-Reply-To: Message from Richard Henderson of "Tue, 26 Mar 2002 14:29:01 PST." <20020326142901.B16366@redhat.com> Date: Tue, 26 Mar 2002 14:37:00 -0000 From: David Edelsohn X-SW-Source: 2002-03/txt/msg00253.txt.bz2 >>>>> Richard Henderson writes: Richard> I think this is a mistake. It is completely unreasonable to have Richard> the entire "major structural changes" time period concurrent with Richard> "please work on making a release happen". Richard> I've been working under the assumption that the current schedule can Richard> be changed, so that I can help Diego with the language independent Richard> tree-ish IL after the 3.1 release. I agree. We do not have enough developer bandwidth to work on major, new changes concurrently with the release process. Even after GCC 3.1.0 is released, we will need to assess how much effort will be required for the GCC 3.1.1 bug-fix release the following quarter. David