Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 85 lines (73 sloc) 3.198 kB
719bcba @wzssyqa Imported Upstream version 2.35~RC6
wzssyqa authored
1
2 Steps in doing an ns release:
3
4 OTCL/TCLCL/NAM RELEASE
5 If necessary, do a otcl,tclcl release. Following are things you need to do for a otcl, tclcl or nam release:
6
7 0. get latest config.sub and config.guess from
8 ftp://ftp.gnu.org/pub/gnu/config/
9 1. update configure (or conf/*) to show current versions of pkgs
10 1.1. re-autoconf if you have changed conf/*
11 1.2. update the windows makefile with "make makefile.vc"
12 (if possible, test this by building under windows
13 2. update CHANGES.html to show when release happens.
14 3. make srctar.
15 4. update CHANGES.html to add a new section for the next pending release.
16 5. nam-- revise the version numbers for Nam and NamGraph in
17 tcl/animator.tcl
18 tcl/nam-default.tcl
19 tcl/www.tcl
20 6. commit the changes
21 7. tag the cvs archive; e.g.:
22 cd otcl; cvs tag OTCL_1_13
23 cd tclcl; cvs tag TCLCL_1_19
24 cd nam-1; cvs tag NAM_1_13
25
26 NS RELEASE
27
28 0.1. figure what the new version
29 0.2. send out release announcement to ns-developers for approval
30 - describe what's new
31 0.3. get latest config.sub and config.guess from
32 ftp://ftp.gnu.org/pub/gnu/config/
33 0.4. Check to make sure conf/configure.in.{otcl,TclCL,tcl,tk}
34 refer to the current versions
35 (For example TclCL_VERS should match the most recent tclcl release,
36 etc.)
37 (re-autoconf ns if you change things in conf/*).
38
39 1.1. make sure test suites all pass
40 1.2. make sure that FILES is up-to-date
41 diff "bin/gen-files" aginst FILES
42 Edit FILES: remove files that are no longer needed and add the
43 new ones; don't add files which are auto-generated
44 2.1. update CHANGES.html to show when the release happens
45 (like the last time it was released)
46 2.2. make sure makefile.vc(WINDOWS) is up to date. If not, do
47 make makefile.vc
48 2.3. "make srctar"
49 4.1. test on new system
50 (build, run test scripts)
51 4.2. Run the same test on a machine other than those of ISI's or even
52 Mash's.
53 5. put the tar in /nfs/web/isi.edu/htdocs/nsnam/dist
54 5. Make a hard link to ~ftp/dist/vint. (For people accessing
55 things via ftp.)
56 5. Put binaries for platforms supported under
57 /nfs/web/isi.edu/htdocs/nsnam/dist/binary
58 5.1. commit all your changes
59 5.2. tag the cvs archive
60 (cd ~ns; cvs tag NS_2_1B6; )
61 6.1. update the web page(s), e.g., "Building NS".
62 6.2. Create a seperate "NS-Problems" section for the new version.
63 7. send out the release announcement (ns-users, ns-announce)
64 (also send to end2end if it's a non-{alpha,beta} release)
65 8. update the VERSION and the BASE-VERSION files to the next version
66 8.1. update CHANGES.html to add a section for the next pending release
67 8.2 commit your changes to the VERSION, BASE-VERSION and CHANGES.html for the next release
68
69
70 NS_ALLINONE RELEASE
71
72 If making a ns-allinone release,
73 1. check if all pkgs (tk,tcl, otcl,tclcl,ns, nam etc) are same as the
74 current available version and change version num in install
75 accordingly
76 2. follow steps as above.
77 3. update install in the cvs under ~ns/allinone
78
79 WEB PAGE UPDATES:
80
81 Update these web pages, or contact someone who has permissions to do so:
82 http://www.isi.edu/nsnam/ns/ns-build.html
83 http://www.isi.edu/nsnam/ns/ns-cygwin.html
84 http://nsnam.isi.edu/nsnam/index.php/Main_Page (News)
Something went wrong with that request. Please try again.