["patch"/rfa/doc] Doco branch commit policy

["patch"/rfa/doc] Doco branch commit policy

[Andrew Cagney]

Another section (this is part of the releasing GDB chapter).  Thoughts?

Andrew


@section Branch commit policy

The branch commit policy is pretty slack. @value{GDBN} releases 5.0, 5.1
and 5.2 all used the below.

@itemize @bullet
@item
the @file{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 then mentioning it in the
@file{gdb/PROBLEMS} file is better than committing a hack
@item
try approval criteria like: does it fix a build; does it fix
the sequence @kbd{break main; run} on a static binary
@item
the further a change is from the core of @value{GDBN} the less likely
the change will worry anyone (i.e. 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 :-)
@end itemize

@emph{Pragmatics: Provided update 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 new architectures or
(within reason) support for a new host are considered acceptable.}

Re: ["patch"/rfa/doc] Doco branch commit policy

[Eli Zaretskii]

> Date: Wed, 06 Mar 2002 21:14:45 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> @item
> the further a change is from the core of @value{GDBN} the less likely
> the change will worry anyone (i.e. target specific code).

You need a "@:" after "i.e.", otherwise TeX will typeset it as a
sentence end.

> This means that changes such as adding a new new architectures or

Two "new"s in a row.