From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27093 invoked by alias); 11 Nov 2011 02:34:35 -0000 Received: (qmail 26999 invoked by uid 22791); 11 Nov 2011 02:34:34 -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; Fri, 11 Nov 2011 02:34:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 1C5B42BB17F; Thu, 10 Nov 2011 21:34:11 -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 pVEXjlIW-iO5; Thu, 10 Nov 2011 21:34:11 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id E5C112BB177; Thu, 10 Nov 2011 21:34:10 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 42490145615; Thu, 10 Nov 2011 21:34:07 -0500 (EST) Date: Fri, 11 Nov 2011 02:34:00 -0000 From: Joel Brobecker To: Yao Qi Cc: gdb-patches@sourceware.org Subject: Re: preparing the upcoming GDB 7.4 release Message-ID: <20111111023407.GE5390@adacore.com> References: <20111107175402.GI14508@adacore.com> <4EBBA2E8.2000203@codesourcery.com> <20111110154311.GA5390@adacore.com> <4EBC85E4.1080706@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EBC85E4.1080706@codesourcery.com> 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-11/txt/msg00306.txt.bz2 > I thought we still have two weeks before branching, looks I am wrong. No, we still have 2 weeks. What I am saying only applies if you think you are not going to make it. > Usually, how long it may take from receiving mail about "preparing the > upcomming GDB X.X release" to branching? and how long from "branching" > to release? I try to give everyone a heads-up before we start the process. How much before, well depends on my good will and how submerged by other work I am... I don't have an alarm in my calendar that says "send email to gdb-patches for XX weeks heads-up on next release branch", but I do enter the tentative dates, and I try to send the email when I think we're getting close. There are several ways you can know about these dates: 1. It's in the "schedule" page, part of the GDB website: http://www.sourceware.org/gdb/schedule/ 2. I make sure we discuss those dates at the end of each release cycle. Usually, not very many people are really interested in the next release date at that stage of the development. But the next cycle is announced. So, although there is the heads-up that I send as a courtesy, you should also be able to plan your work based on the dates published several months in advance. > I don't find anything useful to describe this release process. What else do you want to know? I'll be happy to answer them, and then we can discuss documentation updates wherever you feel more documentation is needed. Bottom line: Just make sure your patches get reviewed and approved before the tentative branch time, and there will be no problem. It looks like it's well under way for your patches. -- Joel