This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[rfa/doc] Branch commit policy
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Fri, 15 Mar 2002 02:30:06 -0500
- Subject: [rfa/doc] Branch commit policy
Hello,
Attached is the revised branch commit policy. Look ok?
Andrew
2002-03-15 Andrew Cagney <ac131313@redhat.com>
* gdbint.texinfo (Releasing GDB): Add the section``Branch Commit
Policy''.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.67
diff -u -r1.67 gdbint.texinfo
--- gdbint.texinfo 2002/03/04 20:38:10 1.67
+++ gdbint.texinfo 2002/03/15 07:28:48
@@ -4822,6 +4822,37 @@
@chapter Releasing @value{GDBN}
@cindex making a new release of gdb
+@section Branch Commit Policy
+
+The branch commit policy is pretty slack. @value{GDBN} releases
+@var{5.0}, @var{5.1} and @var{5.2} all used the below:
+
+@itemize @bullet
+@item
+The @file{gdb/MAINTAINERS} file still holds.
+@item
+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 @file{gdb/PROBLEMS}
+file is better than committing a hack
+@item
+When considering a patch for the branch, suggested criteria include:
+Does it fix a build? Does it fix the sequence @kbd{break main; run}
+when debugging a static binary?
+@item
+The further a change is from the core of @value{GDBN}, the less likely
+the change will worry anyone (e.g.@: target specific code).
+@item
+Only post a proposal to change the core of @value{GDBN} after you've
+sent individual bribes to all the people listed in the
+@file{MAINTAINERS} file @kbd{;-)}
+@end itemize
+
+@emph{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.}
+
+
@section Obsolete any code
Before anything else, poke the other developers (and around the source