From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24368 invoked by alias); 14 Feb 2011 14:50:24 -0000 Received: (qmail 24359 invoked by uid 22791); 14 Feb 2011 14:50:23 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 Feb 2011 14:50:18 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 87A5E2BABDC for ; Mon, 14 Feb 2011 09:50:16 -0500 (EST) 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 5wXOqigsxcI9 for ; Mon, 14 Feb 2011 09:50:16 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 20D0C2BABC2 for ; Mon, 14 Feb 2011 09:50:16 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 363531457E4; Mon, 14 Feb 2011 18:50:10 +0400 (RET) Date: Mon, 14 Feb 2011 14:52:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: time to start thinking about GDB 7.3 (as well!) Message-ID: <20110214145010.GX2384@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00279.txt.bz2 According to the tentative calendar, it's also time to start thinking about the GDB 7.3 release process. Normally, we were planning on branching next week. Judging from the entries in the NEWS file, I think we have enough material to make a new release. However, I also believe that the same issues that we identified as a blocker for 7.2.1 are also relevant for 7.3. There is a Wiki page for the 7.3 release: http://sourceware.org/gdb/wiki/GDB_7.3_Release Can we start putting entries for things we know need to be fixed before branching/release? We should also discuss features that we think would be worthwhile waiting for. Some Python work being finished, for instance, which might nicely complements some of the new enhancements we got? Tracepoints? gdbserver work? Etc. What I propose is to produce 7.2.1 as soon as the blocking issues are fixed. We might also be creating the 7.3 branch pretty much at the same time, which means that 7.3 might be coming shortly after 7.2.1, but I think that's OK. I'd rather not have a 7.2.1 if that means artificially delaying 7.3 - but I don't a problem with producing both. -- Joel