adam/cobm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated, reorganised

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/sc2/code/trunk@1649 8092fc87-c524-0410-9efc-e669fe64eaf9
This commit is contained in:
meep-eep
2005-04-19 02:44:59 +00:00
parent 3b4a8cb373
commit 9dd3061d5d
1 changed files with 33 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sc2/doc/devel/checklist
+33 -16
View File
@@ -1,31 +1,48 @@
Checklist for releases: -== Checklist for releases ==-
- make a final build in release mode
- make sure the permissions in the .zip files are ok (0644 for data files
and 0755 for executables and dirs) Preparing for the release:
- make a new tag for the cvs repository - update the 'version' file in the content dir
- for the source archive: - update 'uqmversion.h'
- use a clean cvs dir. - update uqm.lsm (needs to be done after the content packages are generated)
'cvs export' will produce a clean structure, without CVS dirs. - test on all relevant platforms
This requires a tag having been created though.
Just using 'cvs update' and watching the output will not be
enough, as some files like those beginning with '.#'will be ignored.
- Clean up the Changelog file
- make sure the documentation files are up-to-date - make sure the documentation files are up-to-date
- Whatsnew - Clean up the ChangeLog file
- generate Whatsnew from the ChangeLog
- doc/users/manual.txt - doc/users/manual.txt
- doc/users/unixinstall - doc/users/unixinstall
- Contributing - Contributing
- AUTHORS - AUTHORS
- INSTALL - INSTALL
- unix man pages (in the future) - unix man pages (in the future)
- update the 'version' file in the content dir
- update 'uqmversion.h'
Building the release:
- make a new tag for the cvs repository
- make a final build in release mode
- for the source archive:
- use a clean cvs dir.
'cvs export' will produce a clean structure, without CVS dirs.
This requires a tag having been created though.
Just using 'cvs update' and watching the output will not be
enough, as some files like those beginning with '.#'will be ignored.
- Building the content packages:
- make sure the permissions in the .zip files are ok (0644 for data files
and 0755 for executables and dirs)
- don't compress .ogg files
Announcing the release:
- provide md5 sums for the released files - provide md5 sums for the released files
- add a new entry for the release in the bugs database - add a new entry for the release in the bugs database
- test on all relevant platforms
- update the home page - update the home page
- news - news
- download - download
- send a mail to sc2-announce - send a mail to sc2-announce
Moving on to the next version:
- update the snapshots page so that content diffs are generated to the
most recent release