Mentioning 'cvs export'.

Changed a syntactical error.


git-svn-id: svn://svn.code.sf.net/p/sc2/code/trunk@1196 8092fc87-c524-0410-9efc-e669fe64eaf9
This commit is contained in:
meep-eep
2003-09-05 02:57:23 +00:00
parent 7428eeda56
commit 9a86413eb4
+7 -4
View File
@@ -2,9 +2,13 @@ Checklist for releases:
- make a final build in release mode - make a final build in release mode
- make sure the permissions in the .zip files are ok (0644 for data files - make sure the permissions in the .zip files are ok (0644 for data files
and 0755 for executables and dirs) and 0755 for executables and dirs)
- make a new tag for the cvs repository
- for the source archive: - for the source archive:
- use a clean cvs dir (no .# files) - use a clean cvs dir.
- exclude the CVS dirs themselves from the archive '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.
- Clean up the Changelog file - Clean up the Changelog file
- make sure the documentation files are up-to-date - make sure the documentation files are up-to-date
- Whatsnew - Whatsnew
@@ -14,9 +18,8 @@ Checklist for releases:
- AUTHORS - AUTHORS
- INSTALL - INSTALL
- unix man pages (in the future) - unix man pages (in the future)
- update the 'version' file in the content is up-to-date - update the 'version' file in the content dir
- update 'uqmversion.h' - update 'uqmversion.h'
- make a new tag for the cvs repository
- 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 - test on all relevant platforms