From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4463 invoked by alias); 27 May 2010 00:29:25 -0000 Received: (qmail 4450 invoked by uid 22791); 27 May 2010 00:29:24 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_50 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; Thu, 27 May 2010 00:29:20 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 7D2A72BAC01 for ; Wed, 26 May 2010 20:29:18 -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 pb3Xmo+TrwdQ for ; Wed, 26 May 2010 20:29:18 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3A94E2BAB50 for ; Wed, 26 May 2010 20:29:18 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id ED8B8F58FA; Wed, 26 May 2010 17:29:06 -0700 (PDT) Date: Thu, 27 May 2010 00:29:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: make the GDB 7.2 release sooner? Message-ID: <20100527002906.GG20736@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-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: 2010-05/txt/msg00091.txt.bz2 Hello, Here is a thought that came to me while looking at the schedule for a possible 7.1.1: - There are only a couple of patches that went into the 7.1 branch since the 7.1 release, so I'm not sure whether it's worth making that release or not. I certainly don't mind. We have another month before the planned date for that corrective release. - There has been a lot of improvements on the Python API side of things recently, and I think it'd be nice to release that sooner rather than later. So, my proposal is to move the 7.2 release date up a few months to, say, end of June. That should give us ample time to finish up whatever was in the works (tracepoints? more Python scripts? etc), before we start the release process. What triggered this suggestion is python, but we do have lots of other things that are worth mentioning (in fact, everything in the NEWS files is worth mentioning), but to summarize: - Access to Windows Thread Information Block - Symbian OS support - D language support - New GDBserver features and new remote packets - some user-level improvements on various commands; of interest to some is a new "save breakpoints" command. I should also say that this is independent of whether we decide to do a 7.1.1 release or not. I'm willing to release both if that makes sense. Thoughts? -- Joel