[wip] How to release section

[Andrew Cagney <ac131313 at cygnus dot com>]

Hello,

Attached is a (very obviously) work in progress patch for the internals 
manual going through how to release GDB.

enjoy,
Andrew
2002-01-15  Andrew Cagney  <ac131313@redhat.com>

	* gdbint.texinfo (Releasing GDB): New chapter.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.53
diff -p -r1.53 gdbint.texinfo
*** gdbint.texinfo	2002/01/15 01:29:24	1.53
--- gdbint.texinfo	2002/01/15 05:15:43
*************** as the mechanisms that adapt @value{GDBN
*** 93,98 ****
--- 93,99 ----
  * Support Libraries::
  * Coding::
  * Porting GDB::
+ * Releasing GDB::
  * Testsuite::
  * Hints::
  * Index::
*************** distribution, generate @file{gdb-all.tex
*** 4820,4825 ****
--- 4821,4973 ----
  files @file{gdb.info*} in the distribution.  Note the plural;
  @code{makeinfo} will split the document into one overall file and five
  or so included files.
+ 
+ @node Releasing GDB
+ 
+ @chapter Releasing @value{GDBN}
+ @cindex making a new release of gdb
+ 
+ @section Before the branch
+ 
+ Mark as OBSOLETE any uninteresting targets or code files.  This has a
+ number of steps and is slow - mainly to ensure that people have had a
+ reasonable chance to respond.  Remember, everything on the internet
+ takes a week.
+ 
+ @itemize @bullet
+ @item
+ announce the change on gdb@
+ @item
+ wait a week
+ @item
+ announce the change on gdb-announce@
+ @item
+ wait a week or so
+ @item
+ post / commit the change
+ @end itemize
+ 
+ Organize the schedule.
+ 
+ @itemize @bullet
+ @item
+ announce it
+ @item
+ wait a week
+ @item
+ announce branch date
+ @item
+ wait a week
+ @item
+ you want to encourage people to sanity check their build as you really
+ don't want to be contending with configury problems as getting them
+ committed is complicated.
+ @item
+ Cut the branch
+ @item
+ wait a week
+ @item
+ start enjoying all the fun
+ @end itemize
+ 
+ As an aside, the branch tag name is probably regrettable vis:
+ gdb_N_M-YYYY-MM-DD-@{branch,branchpoint@}.
+ 
+ 
+ @section Building a Release
+ 
+ @subheading Establish a few defaults.
+ 
+ @example
+ $  b=gdb_5_1_0_1-2002-01-03-branch
+ $  v=5.1.0.1
+ $  cd /sourceware/snapshot-tmp/gdbadmin-tmp/$b
+ $  which autoconf
+ /home/gdbadmin/bin/autoconf
+ @end example
+ 
+ NB: Check the autoconf version carefully.  You want to be using
+ gdbadmin's version (which is really the version taken from the binutils
+ snapshot).  SWARE may have a different version installed.
+ 
+ @subheading Check out the relevant modules:
+ 
+ @example
+ $  for m in gdb insight dejagnu; do
+ ( mkdir -p $m && cd $m && cvs -q -f -d /cvs/src co -P -r $b $m )
+ done
+ @end example
+ 
+ NB: The reading of .cvsrc is disabled (-f) so that there isn't any
+ confusion between what is written here and what CVS really does.
+ 
+ @subheading Update the file gdb/version.in where applicable.
+ 
+ @example
+ $  for m in gdb insight; do echo $v > $m/src/gdb/version.in ; done
+ @end example
+ 
+ @subheading Mutter something about creating a ChangeLog entry. (both trunk and branch).
+ 
+ @example
+ $  emacs gdb/src/gdb/version.in
+ c-x 4 a
+ Bump version to 5.1.0.1.
+ c-x c-s c-x c-c
+ ditto for insight/src/gdb/version.in
+ @end example
+ 
+ @subheading Mutter something about updating README
+ 
+ For dejagnu, edit ``dejagnu/src/dejagnu/configure.in'' and set it to
+ gdb-$v and then regenerate configure.  Mention this in the dejagnu
+ ChangeLog.
+ 
+ @example
+ $  emacs dejagnu/src/dejagnu/configure.in
+ ...
+ c-x 4 a
+ Bump version to 5.1.0.1.
+ * configure: Re-generate.
+ c-x c-s c-x c-c
+ $  ( cd dejagnu/src/dejagnu && autoconf )
+ @end example
+ 
+ @subheading Build the snapshot:
+ 
+ @example
+ $  for m in gdb insight dejagnu; do
+ ( cd $m/src && gmake -f Makefile.in $m.tar.bz2 )
+ done
+ @end example
+ 
+ @subheading Do another CVS update to see what the damage is.
+ 
+ @example
+ $  ( cd gdb/src && cvs -q update )
+ @end example
+ 
+ You're looking for files that have mysteriously disappeared as the
+ distclean has the habit of deleting files it shouldn't.
+ 
+ @subheading Copy all the .bz2 files to the ftp directory:
+ 
+ @example
+ cp */src/*.bz2 ~ftp/.....
+ @end example
+ 
+ @subheading Something about gzip'ing them.
+ 
+ @subheading Something about web pages?
+ 
+ @subheading Something about documentation?
+ 
+ @subheading Something about committing _all_ the generated files.
+ 
+ @section After the release
+ 
+ Remove any OBSOLETE code.
+ 
  
  @node Testsuite