From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13694 invoked by alias); 29 Aug 2002 15:37:53 -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 13687 invoked from network); 29 Aug 2002 15:37:52 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 29 Aug 2002 15:37:52 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8B78A3CAD for ; Thu, 29 Aug 2002 11:37:50 -0400 (EDT) Message-ID: <3D6E3FCE.5080500@ges.redhat.com> Date: Thu, 29 Aug 2002 08:37:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: GDB 5.3 Branch 4th Sept 00:00 GMT Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00398.txt.bz2 Hello, It looks like this date is going to hold. I'll cut the branch using `-D 2002-09-04' probably 12-24 hrs after the event. This lets me look back at what was happening around 2002-09-04-gmt and decide if making the cut really is a good idea :-) 15.2 Branch Commit Policy http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC132 The branch commit policy is pretty slack. GDB releases 5.0, 5.1 and 5.2 all used the below: * The `gdb/MAINTAINERS' file still holds. * Don't fix something on the branch unless/until it is also fixed in the trunk. If this isn't possible, mentioning it in the `gdb/PROBLEMS' file is better than committing a hack. * When considering a patch for the branch, suggested criteria include: Does it fix a build? Does it fix the sequence break main; run when debugging a static binary? * The further a change is from the core of GDB, the less likely the change will worry anyone (e.g., target specific code). * Only post a proposal to change the core of GDB after you've sent individual bribes to all the people listed in the `MAINTAINERS' file ;-) Pragmatics: Provided updates are restricted to non-core functionality there is little chance that a broken change will be fatal. This means that changes such as adding a new architectures or (within reason) support for a new host are considered acceptable. A guess at date for the next release (5.4/6.0) is March '03. http://sources.redhat.com/gdb/schedule/ enjoy, Andrew