This page was produced by an automated import process, and may have formatting errors; feel free to fix.
Before the Branch
The most important objective at this stage is to find and fix simple changes that become a pain to track once the branch is created. For instance, configuration problems that stop GDB from even building. If you can’t get the problem fixed, document it in the gdb/PROBLEMS file. [Prompt-for-gdb_002fNEWS ]
Prompt for {{{gdb/NEWS}}}
People always forget. Send a post reminding them but also if you know something interesting happened add it yourself. The schedule script will mention this in its e-mail. [Review-gdb_002fREADME ]
Review {{{gdb/README}}}
Grab one of the nightly snapshots and then walk through the gdb/README looking for anything that can be improved. The schedule script will mention this in its e-mail. [Refresh-any-imported-files_002e ]
Refresh any imported files.
A number of files are taken from external repositories. They include:
texinfo/texinfo.tex
config.guess et. al. (see the top-level MAINTAINERS file)
etc/standards.texi, etc/make-stds.texi [Check-the-ARI ]
Check the ARI
[http://sourceware.org/gdb/ari A.R.I.] is an awk script (Awk Regression Index
that checks for a number of errors and coding conventions. The checks include things like using malloc instead of xmalloc and file naming problems. There shouldn’t be any regressions. [Review-the-bug-data-base ]
Review the bug data base
Close anything obviously fixed. [Check-all-cross-targets-build ]
Check all cross targets build
The targets are listed in gdb/MAINTAINERS.