From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9030 invoked by alias); 22 Nov 2013 02:19:18 -0000 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 Received: (qmail 9009 invoked by uid 89); 22 Nov 2013 02:19:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: rock.gnat.com Received: from Unknown (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 22 Nov 2013 02:19:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EC1B61161D6; Thu, 21 Nov 2013 21:19:42 -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 j63HGpjimmYJ; Thu, 21 Nov 2013 21:19:42 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 5DC901161BA; Thu, 21 Nov 2013 21:19:42 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 3DD83E16B7; Fri, 22 Nov 2013 06:19:04 +0400 (RET) Date: Fri, 22 Nov 2013 03:02:00 -0000 From: Joel Brobecker To: "Maciej W. Rozycki" , Tom Tromey Cc: Tristan Gingold , Richard Sandiford , binutils@sourceware.org, gdb-patches@sourceware.org Subject: Re: Release 2.24 Message-ID: <20131122021904.GN3481@adacore.com> References: <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com> <20130918213245.GO3132@adacore.com> <20131118172117.GD3481@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-11/txt/msg00667.txt.bz2 > Although if you expect the delay between binutils 2.24 and GDB 7.7 to > stay within a couple weeks, e.g. if you think you'll be able to roll the > latter out by say mid December, We might be able to achieve that timeframe, but it would be very hard for me to guaranty it. From past experience, event if we started today, I don't remember any release cycle that took less than a month so we are already looking at a Xmas release at best. Here is what I propose: . Let's confirm the list of patches needed for the 7.6 branch (is there just the one in binutils?) . Get them approved, and pushed to the gdb_7_6-branch . I will need from you a small description of what this release is about. It will save me time and make sure I also don't say something incorrect if I can just copy/paste that text directly in the web + email announcements. . Once that's done, I have 2 options: (1) Create the new relase off the git repository, but create the release either manually or with the new scripts; (2) Push the commit to the CVS repo, and re-use the old scripts to make the release. If it's only a handful of patches, my preference would be to play it safe, and go with option (2). Pushing the patches to the CVS repo is super easy thanks to "git cvsexportcommit", but we will need the help of someone like Tom to temporary re-open the CVS (or, if Tom prefers, he can cvsexportcommit the patches himself, and let us know when he is done). Thoughts? Tom? -- Joel