From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29479 invoked by alias); 10 Feb 2002 02:13:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29413 invoked from network); 10 Feb 2002 02:13:54 -0000 Received: from unknown (HELO localhost.redhat.com) (24.114.26.18) by sources.redhat.com with SMTP; 10 Feb 2002 02:13:54 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id ADAC53E6A; Sat, 9 Feb 2002 21:13:50 -0500 (EST) Message-ID: <3C65D75D.5020900@cygnus.com> Date: Sat, 09 Feb 2002 18:13:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: GDB 5.2 et.al. release schedule References: <3C4F228A.4010803@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00166.txt.bz2 > See also: http://gcc.gnu.org/develop.html > > There have been plenty of concerns raised about the unreliability of the GDB release cycle: 12 months, 18 months, ... I'm looking for more robust ways of addressing this. (btw the 5.2 release manager role is still available) (I promise not to break an arm again :-). (I've had a very welcome expression of interest for the release role). > In previous e-mail I've mentioned the intention to branch 5.2 mid Feb and release it mid March. > > With those two points in mind, and looking across at GCC for idea's, I'd like to propose that GDB have a more formal release schedule. > > I should note that GDB 5.1 established a new precident - it was released with several targets (HP/UX, ALPHA) known to be broken. Being willing to do this greatly simplified the task of the release person as they should no longer feel guilty when documenting that certain targets/natives just don't work. > > GCC's cycle is every 6 months. GDB could go for 12, 6, 4, or 3 months. In the below I've somewhat arbitrarially chosen 4 months. That would give three major and (possibly) three minor releases a year. > > 01 Jan - 5.1.1 > 02 Feb - branch (5.2) > 03 Mar - release (5.2) > 04 Apr > 05 May - 5.2.x? > 06 Jun - branch (5.3) > 07 Jul - release (5.3) > 08 Aug > 09 Sep - 5.3.x? > 10 Oct - branch (5.4) > 11 Nov - release (5.4) > 12 Dec No objections (I guess everyone knows it is me that gets to do this). I've added cronjobs to send out reminders of the branch and release dates. The branch reminder (branch in two weeks) should appear in about a week. Andrew