776
|
1 |
Steps in doing an ns-3 release
|
|
2 |
|
|
3 |
1. prepare the source files
|
|
4 |
- revise and check in AUTHORS, if needed
|
|
5 |
- revise and check in RELEASE_NOTES
|
|
6 |
- update and check in VERSION to the latest release number
|
|
7 |
2. make a new "architecture.pdf" document and place it in the doc/ directory
|
932
|
8 |
3. add current version of waf script from subversion:
|
|
9 |
- svn checkout http://waf.googlecode.com/svn/tags/ns3/ waf
|
|
10 |
- build waf script and put it into top of ns-3-dev
|
|
11 |
4. cd ns-3-dev; ./waf configure; ./waf dist
|
|
12 |
5. test tarball on release platforms (run-tests and simple-p2p)
|
|
13 |
6. tag ns-3-dev with "release ns-3.0.X"
|
|
14 |
- hg tag "release ns-3.0.x"
|
|
15 |
- hg push
|
|
16 |
7. clone the tagged ns-3-dev and place it on the repository
|
|
17 |
- ssh code.nsnam.org; sudo; su code;
|
|
18 |
- cp -r /home/code/repos/ns-3-dev /home/code/repos/ns-3.0.x
|
|
19 |
- cd /home/code/repos/ns-3.0.x/.hg and edit the hgrc appropriately
|
|
20 |
8. upload "ns-3.0.x.tar.bz2" to the releases/ directory on the server
|
|
21 |
9. update web page
|
776
|
22 |
- add link to news.html
|
|
23 |
- update download.html
|
|
24 |
- update roadmap.html
|
|
25 |
- build and update Doxygen directory on the server
|
|
26 |
- update and upload software architecture document (PDF, HTML)
|
932
|
27 |
10. announce to ns-developers, with summary of release notes
|