From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14014 invoked by alias); 11 Nov 2011 05:58:40 -0000 Received: (qmail 14005 invoked by uid 22791); 11 Nov 2011 05:58:38 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 11 Nov 2011 05:58:24 +0000 Received: from nat-jpt.mentorg.com ([192.94.33.2] helo=PR1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1ROk87-00002L-D0 from Yao_Qi@mentor.com ; Thu, 10 Nov 2011 21:58:23 -0800 Received: from [127.0.0.1] ([172.16.63.104]) by PR1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 Nov 2011 14:58:21 +0900 Message-ID: <4EBCB979.3020700@codesourcery.com> Date: Fri, 11 Nov 2011 05:58:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: Joel Brobecker CC: gdb-patches@sourceware.org Subject: Re: preparing the upcoming GDB 7.4 release References: <20111107175402.GI14508@adacore.com> <4EBBA2E8.2000203@codesourcery.com> <20111110154311.GA5390@adacore.com> <4EBC85E4.1080706@codesourcery.com> <20111111023407.GE5390@adacore.com> In-Reply-To: <20111111023407.GE5390@adacore.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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/msg00308.txt.bz2 On 11/11/2011 10:34 AM, Joel Brobecker wrote: > 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/ That is what I want, thanks. >> > 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. I am clear now, but there may be someone else asking something similar in the future. Questions/answers in this thread are quite representative. We can gather them and put them down in the wiki or somewhere else. Something in my mind (I am not good at wording) "For each upcoming release, we should be more careful about the changes. If you propose to add a new port of gdb, unless you are touching some of the core code (the parts that are not target or arch specific), it's usually OK to accept a port even after the branch was made. For new features, you need to convince the Global Maintainers as a group that there is a good reason for waiting. Reasons could be: - It's only going to be a few more days at most - Some other features would not be usable without it - It's a killer feature " -- Yao (齐尧)