From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2818 invoked by alias); 30 Jan 2009 00:48:31 -0000 Received: (qmail 2810 invoked by uid 22791); 30 Jan 2009 00:48:31 -0000 X-SWARE-Spam-Status: No, hits=-2.4 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; Fri, 30 Jan 2009 00:48:26 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E229B2A964F; Thu, 29 Jan 2009 19:48:24 -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 7kJ8Cm6HuMM4; Thu, 29 Jan 2009 19:48:24 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 704082A964D; Thu, 29 Jan 2009 19:48:24 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id D5727E7ACD; Thu, 29 Jan 2009 16:48:21 -0800 (PST) Date: Fri, 30 Jan 2009 00:48:00 -0000 From: Joel Brobecker To: Michael Snyder Cc: Marc Khouzam , teawater , David Daney , "gdb@sourceware.org" Subject: Re: Discussing the next GDB release (GDB 7.0?) Message-ID: <20090130004821.GC14194@adacore.com> References: <20090116033948.GI31296@adacore.com> <6D19CA8D71C89C43A057926FE0D4ADAA06C52409@ecamlmw720.eamcs.ericsson.se> <497E9260.90203@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497E9260.90203@vmware.com> 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: 2009-01/txt/msg00186.txt.bz2 > >For what its worth, I can't speak to the level of criticality of > >process record and replay, but we would really like to see this in > >the 7.0 release. > > Ditto! I just got back home in Vancouver, so I haven't followed the list too closely, but it looks like review of the associated patches has started. Otherwise, do you think you could lend a hand? The parameters are as follow: I am trying to determine what's blocking before we can start the release process. Other than that, I'm trying to release as early as possible, because the last release was a long while ago. Other than that, I am not opposed to any feature in the next release - it's just a mtter of getting them in before we branch. Once the branch is created, however, the Global Maintainers and I will start moderating what goes to the branch. -- Joel