/[gnue]/gnue-common/doc/technotes/00011.txt
ViewVC logotype

Diff of /gnue-common/doc/technotes/00011.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by reinhard, Fri Oct 17 16:13:46 2003 UTC revision 1.3 by reinhard, Tue Oct 21 13:28:27 2003 UTC
# Line 10  How to make a release Line 10  How to make a release
10    code.    code.
11    
12  * Read all documentation and check if is consistent with the current state of  * Read all documentation and check if is consistent with the current state of
13    the code (this includes doc/, AUTHORS, FAQ, INSTALL, README, ROADMAP, THANKS    the code (this includes doc/, AUTHORS, BUGS, FAQ, INSTALL, README, ROADMAP,
14    and TODO).    THANKS and TODO).
15    
16  * Check if setup.py needs to be updated because of changes since the last  * Check if setup.py needs to be updated because of changes since the last
17    release (files added, files removed, ...).    release (files added, files removed, ...).
18    
19  * Do a test sdist, build and install of the *.99 release.  * Commit everything to CVS.
   Use 'GNUE_VERSION_SUFFIX=-pre1 ./setup.py sdist --format="gztar,zip"'  
   to create the tarball  
20    
21  * "cvs commit" everything now.  * Create the tarballs for the prerelease:
22      "GNUE_VERSION_SUFFIX=-pre1 ./setup.py sdist --format='gztar,zip'"
23    
24  * Let the packagers test packaging of the *.99 release.  * Post the prerelease to the web:
25      "scp dist/* $LOGNAME@www.gnuenterprise.org:/var/www/downloads/prereleases"
26    
27  * Run "cvs2cl --ignore ChangeLog --ignore README.cvs --ignore INSTALL.cvs \  * Test installing the prerelease from tarball on different systems.
28    
29    * Let the packagers test packaging of the prerelease.
30    
31    * Update the ChangeLog file:
32      "cvs2cl --ignore ChangeLog --ignore README.cvs --ignore INSTALL.cvs \
33    --ignore MANIFEST.in --ignore .cvsignore --ignore postweb"    --ignore MANIFEST.in --ignore .cvsignore --ignore postweb"
   to update the ChangeLog.  
34    
35  * Update the NEWS file.  * Update the NEWS file.
36    
# Line 35  How to make a release Line 39  How to make a release
39  * Add an entry to the top of ChangeLog that says  * Add an entry to the top of ChangeLog that says
40    "* NEWS, src/__init__.py: Released x.x.x.".    "* NEWS, src/__init__.py: Released x.x.x.".
41    
42  * "cvs commit" everything now.  * Commit everything to CVS.
43    
44  * Run setup.py sdist --format="gztar,zip".  * Create the tarballs for the release:
45      "setup.py sdist --format='gztar,zip'"
46    
47  * Tag CVS.  * Tag CVS.
48    "cvs tag common-x-x-x-release" or "cvs tag appserver-x-x-x-release" etc.    "cvs tag common-x-x-x-release" or "cvs tag appserver-x-x-x-release" etc.
49    
50  * Post tarfiles to the website  * Post the release to the web and remove the prerelease:
51    "scp dist/* $LOGNAME@www.gnuenterprise.org:/var/www/downloads/releases"    "scp dist/* $LOGNAME@www.gnuenterprise.org:/var/www/downloads/releases"
52    on www.gnuenterprise.org make a symbolic link from releases to current    on www.gnuenterprise.org:
53      ln -s /var/www/downloads/releases/<filename>.* /var/www/downloads/current
54      rm -f /var/www/downloads/prereleases/<filename>.*
55    
56  * Post documentation to the website using the "postweb" script  * Post documentation to the website using the "postweb" script
57    
58  * In src/__init__.py, set _version to the next version number, and _release to  * In src/__init__.py, set _version to the next version number, and _release to
59    0.    0.
60    
61  * cvs commit  * Commit everything to CVS.

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26