From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16210 invoked by alias); 26 Jan 2008 00:53:41 -0000 Received: (qmail 16202 invoked by uid 22791); 26 Jan 2008 00:53:41 -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; Sat, 26 Jan 2008 00:53:23 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EB6FA2A968A for ; Fri, 25 Jan 2008 19:53:21 -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 VumxGRSonerY for ; Fri, 25 Jan 2008 19:53:21 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B09972A9683 for ; Fri, 25 Jan 2008 19:53:21 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 9D4B4E7ACB; Fri, 25 Jan 2008 16:53:19 -0800 (PST) Date: Sat, 26 Jan 2008 00:53:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: Our next GDB release (GDB version 6.8) Message-ID: <20080126005319.GD21874@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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-01/txt/msg00260.txt.bz2 Hello GDB enthusiasts! The schedule on the GDB website shows that we were planning on making a new GDB release (GDB version 6.8) soon: Branch creation on Feb 5th, and a then an official release a month later. Looks like it's going to be tight to make these dates, but I don't think it's a problem. I would like us to start drawing a list of things that we'd like to include in that release. For one, I'd like to list the changes I submitted regarding Ada support, at least the ones that provide the most value. Maybe I'll also find some time to work on something we briefly discussed a few years back regarding the README file, and maybe think about the NEWS file too. That's not critical though, just making the release slightly more labor intensive. I propose we use a wiki page again. In fact, I was surprised to see that someone already created one. Should I thank Nick for that? Opinions? Items that should be put on the list of things to finish for the release? Please send them here and I'll add them to the wiki. If a thread was already started, please post a link to it as well. Thanks, -- Joel