From 2d135d4f85a88d2d268debed4aab39b0fca9e433 Mon Sep 17 00:00:00 2001
From: Craig Dowell <craigdo@ee.washington.edu>
Date: Fri, 9 Oct 2009 21:28:50 -0700
Subject: [PATCH] Update release steps

---
 doc/release_steps.txt | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/doc/release_steps.txt b/doc/release_steps.txt
index d46761fe6..a10ebfc83 100644
--- a/doc/release_steps.txt
+++ b/doc/release_steps.txt
@@ -1,13 +1,18 @@
 Steps in doing an ns-3 release
 
 1. check out a clean ns-3-dev somewhere
+   - hg clone http://code.nsnam.org/ns-3-allinone
+   - ./download.py
+   - ./build.py
+   - confirm that the release builds cleanly.
+   - ensure that tests pass (./test.py)
+   - ensure no regressions (./waf --regression)
 2. prepare the source files
    - revise and check in AUTHORS, if needed
    - revise and check in RELEASE_NOTES
    - DO NOT change VERSION at this time
    - confirm that Doxygen builds cleanly and without warnings
-     (./waf --check; ./waf --doxygen), and check in any necessary changes 
-   - ensure no regressions (./waf --regression)
+     (./waf doxygen), and check in any necessary changes 
 3. ./waf configure; ./waf dist
    - this will create an ns-3-dev.tar.bz2 tarball
    - this will also create a ns-3-dev-ref-traces.tar.bz2 tarball
@@ -34,13 +39,17 @@ Steps in doing an ns-3 release
      for the regression tests to work.
    - hg commit
    - hg push
-9. Run the regression tests on the new release (debug and optimized)
+9. Run the tests on the new release (debug and optimized)
    - ./waf -d debug configure
    - ./waf
+   - ./test.py
+   - ./test.py -g
    - ./waf --regression
    - ./waf --valgrind --regression (for valgrind version)
    - ./waf -d optimized configure
    - ./waf
+   - ./test.py
+   - ./test.py -g
    - ./waf --regression
    - ./waf --valgrind --regression (for valgrind version)
    - There should be no regression errors at this time