36 lines
1.6 KiB
Plaintext
36 lines
1.6 KiB
Plaintext
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; 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 600 permissions, and user/group = apache
|
|
8. 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
|
|
9. announce to ns-developers, with summary of release notes
|