doc/release_steps.txt
author Mathieu Lacage <mathieu.lacage@sophia.inria.fr>
Thu, 13 Mar 2008 12:56:49 -0700
changeset 2602 d9262bff6df2
parent 2343 85959d329c8c
child 2865 d40eb18a4da0
permissions -rw-r--r--
add back support for introspected doxygen.

Steps in doing an ns-3 release

0. check out a clean ns-3-dev somewhere
1. prepare the source files
   - revise and check in AUTHORS, if needed
   - revise and check in RELEASE_NOTES
   - update and check in VERSION to the latest release number
   - confirm that Doxygen builds cleanly and without warnings
     (./waf --doxygen), and check in any necessary changes 
2. ./waf configure; ./waf dist
   - this will create a ns-3.0.x.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 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"
6. upload "ns-3.0.x.tar.bz2" to the /var/www/html/releases/ directory on 
   the www.nsnam.org server
   - give it 644 file permissions, and user/group = apache
7. update web pages on www.nsnam.org (source is in the www/ module)
   - add link to news.html
   - update getting_started.html
   - update documents.html
   - update roadmap on wiki
   - build and update Doxygen directory on the server
     -- ssh www.nsnam.org; sudo tcsh; su nsnam;
     -- edit ~/bin/update-doxygen-release file and change RELEASE variable 
        to the right version number 
     -- run ~/bin/update-doxygen-release
8. announce to ns-developers, with summary of release notes