From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13582 invoked by alias); 22 Sep 2008 17:22:19 -0000 Received: (qmail 13571 invoked by uid 22791); 22 Sep 2008 17:22:19 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 22 Sep 2008 17:21:29 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 717A72A967D; Mon, 22 Sep 2008 13:21:27 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wpL2ryhuKxV0; Mon, 22 Sep 2008 13:21:27 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 365B52A9663; Mon, 22 Sep 2008 13:21:27 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id E1C53E7ACD; Mon, 22 Sep 2008 10:21:24 -0700 (PDT) Date: Mon, 22 Sep 2008 17:22:00 -0000 From: Joel Brobecker To: Marc Khouzam Cc: gdb@sourceware.org Subject: Re: GDB Scheduled Release page Message-ID: <20080922172124.GG2685@adacore.com> References: <6D19CA8D71C89C43A057926FE0D4ADAA06294045@ecamlmw720.eamcs.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06294045@ecamlmw720.eamcs.ericsson.se> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-09/txt/msg00126.txt.bz2 > The GDB release schedule page (http://sourceware.org/gdb/schedule) > hasn't been updated for a while, it seems. Is there another source > of information for the release schedule, where I can point interested > individuals? Or will this page be udpated? It's because we haven't completely decided on a rough date yet. We discussed it at the GCC Summit, and the consensus is that we wanted to wait for the Python work to be submitted, give it a little time to stabilize and grow, etc. I think there might have been other major features that were included in the list of nice-to-have. This means that we're thinking of a new release early next year, I think. -- Joel