[csms-cvs] csms-core/src/documentation Release-Checklist.txt,1.2,1.3

[<rga...@us...>]

Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv18292

Modified Files:
	Release-Checklist.txt 
Log Message:
improve layout


Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** Release-Checklist.txt	18 Oct 2002 17:07:22 -0000	1.2
--- Release-Checklist.txt	18 Oct 2002 21:09:15 -0000	1.3
***************
*** 1,26 ****
  - update docbook stylesheets (see bug 155 for process)
  - cent clean all
  - Check for any errors in the unit test reports
    - correct any failures and start again from build clean
  - update ./src/status.xml 
           - add date to release element
           - move tasks to the necessary release element
           - create a new release element (with a due date)
  - update ./module.xml
           - set version tag to beta, rc1, rc2 etc.
           - check dependiencies list is complete
  - update ./legal
           - ensure licenses for all libs are included
  - update the web site docs
  - cent deploysite
  - ensure CVS is up to date
  - tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
           - create a branch for this release?
! - sign distributions
  - publish web site
  - update ./module.xml
           - increment version number and set tag to alpha
  - Generate announcements and HEADER.html
  - upload distributions to correct dir
  - send announcements to ...
    ...
--- 1,39 ----
  - update docbook stylesheets (see bug 155 for process)
+ 
  - cent clean all
+ 
  - Check for any errors in the unit test reports
    - correct any failures and start again from build clean
+ 
  - update ./src/status.xml 
           - add date to release element
           - move tasks to the necessary release element
           - create a new release element (with a due date)
+ 
  - update ./module.xml
           - set version tag to beta, rc1, rc2 etc.
           - check dependiencies list is complete
+ 
  - update ./legal
           - ensure licenses for all libs are included
+ 
  - update the web site docs
+ 
  - cent deploysite
+ 
  - ensure CVS is up to date
+ 
  - tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
           - create a branch for this release?
! 
  - publish web site
+ 
  - update ./module.xml
           - increment version number and set tag to alpha
+ 
  - Generate announcements and HEADER.html
+ 
  - upload distributions to correct dir
+ 
  - send announcements to ...
    ...