Mercurial Mercurial > ns-3.5 / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | zip | gz | bz2 | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
plug more holes in release steps
authorCraig Dowell <craigdo@ee.washington.edu>
Tue, 17 Jun 2008 12:52:46 -0700
changeset 3280 25fbf06f9a56
parent 3279 61d5b66cdb25
child 3281 bc61af712d6e
plug more holes in release steps
doc/release_steps.txt file | annotate | diff | comparison | revisions
wscript file | annotate | diff | comparison | revisions 
--- a/doc/release_steps.txt	Tue Jun 17 11:57:27 2008 -0700
+++ b/doc/release_steps.txt	Tue Jun 17 12:52:46 2008 -0700
@@ -8,34 +8,36 @@
    - confirm that Doxygen builds cleanly and without warnings
      (./waf check; ./waf --doxygen), and check in any necessary changes 
    - ensure no regressions (./waf --regression)
+   - update the wscript in ns-3-dev to point REGRESSION_TRACES_TAR_NAME and
+     REGRESSION_TRACES_DIR_NAME to the correct places.
 2. ./waf configure; ./waf dist
-   - this will create a ns-3.0.x.tar.bz2 tarball
-   - this will also create a ns-3.0.x-ref-traces.tar.bz2 tarball
+   - this will create a ns-3.1x.tar.bz2 tarball
+   - this will also create a ns-3.1x-ref-traces.tar.bz2 tarball
 3. test tarball on release platforms (waf check and maybe some other scripts)
 4. once you are happy with the tarball, tag ns-3-dev with "release ns-3.0.X"
-   - hg tag "release ns-3.0.x"
+   - hg tag "release ns-3.1x"
    - hg push 
 5. clone the tagged ns-3-dev and place it on the repository
    - ssh code.nsnam.org; sudo tcsh; su code;
-   - cp -r /home/code/repos/ns-3-dev /home/code/repos/ns-3.0.x
-   - cd /home/code/repos/ns-3.0.x/.hg and edit the hgrc appropriately:
-     "description = ns-3.0.x release
-      name = ns-3.0.x"
+   - cp -r /home/code/repos/ns-3-dev /home/code/repos/ns-3.1x
+   - cd /home/code/repos/ns-3.1x/.hg and edit the hgrc appropriately:
+     "description = ns-3.1x release
+      name = ns-3.1x"
 6. Run the regression tests on the new release and update the reference traces
    - ./waf --regression
    - ./waf --valgrind --regression (for valgrind version)
    - There should be no regression errors at this time
-   - tag ns-3-dev-ref-traces with "release ns-3.0.X"
-     hg tag "release ns-3.0.x"
+   - tag ns-3-dev-ref-traces with "release ns-3.1X"
+     hg tag "release ns-3.1x"
      hg push
    - clone the ns-3-dev-ref-traces and place it on the repository as in step
-     5 but use the name ns-3.0.x-ref-traces
+     5 but use the name ns-3.1x-ref-traces
 7. Create a reference traces tarball
    - again, run "./waf dist" 
-8. upload "ns-3.0.x.tar.bz2" to the /var/www/html/releases/ directory on 
+8. upload "ns-3.1x.tar.bz2" to the /var/www/html/releases/ directory on 
    the www.nsnam.org server
    - give it 644 file permissions, and user/group = apache
-9. upload "ns-3.0.x-ref-traces.tar.bz2" to the /var/www/html/releases/ 
+9. upload "ns-3.1x-ref-traces.tar.bz2" to the /var/www/html/releases/ 
    directory on the www.nsnam.org server
    - give it 644 file permissions, and user/group = apache
 10. update web pages on www.nsnam.org (source is in the www/ module)
--- a/wscript	Tue Jun 17 11:57:27 2008 -0700
+++ b/wscript	Tue Jun 17 12:52:46 2008 -0700
@@ -34,7 +34,7 @@
 # mercurial on the system.  It is expected to be created using tar -cjf and
 # will be extracted using tar -xjf
 #
-REGRESSION_TRACES_TAR_NAME  = "ns-3.0.12-ref-traces.tar.bz2"
+REGRESSION_TRACES_TAR_NAME  = "ns-3.1-RC1-ref-traces.tar.bz2"
 
 #
 # The path to the Mercurial repository used to find the reference traces if
@@ -47,7 +47,7 @@
 # The local directory name (relative to the 'regression' dir) into
 # which the reference traces will go in either case (net or hg).
 #
-REGRESSION_TRACES_DIR_NAME = "ns-3-dev-ref-traces"
+REGRESSION_TRACES_DIR_NAME = "ns-3.1-RC1-ref-traces"
 
 
 def dist_hook():
ns-3.5