Developer's Guide: refresh release procedures
commitdc342f45f6c8ec02431495863687b3638f1646d5
authorDavid Brownell <dbrownell@users.sourceforge.net>
Mon, 22 Feb 2010 00:55:17 +0000 (21 16:55 -0800)
committerDavid Brownell <dbrownell@users.sourceforge.net>
Mon, 22 Feb 2010 00:55:17 +0000 (21 16:55 -0800)
tree99be18c25f9f1208b1ac939e193986449307707d
parentc8ea748dc22660dad934537384d35903dfcc492e
Developer's Guide: refresh release procedures

Be a closer match to what I've actually done for the past few cycles.

In particular, hold off pushing repository updates until after the
packages are published, as part of opening the merge window, and
mention the utility commands which actually create the archives.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
doc/manual/release.txt