INSTRUCTIONS FOR PREPARING STANDARD RELEASES OF SCOPE

When your code is ready to be released follow this instructions

1. Check what is the next release name (number) and set it in RELEASE
variable in Makefile. Always release several release candidates
("\-rc[0..9]$") bcs it is easy to screw up things.

2. Write release notes and enter the name in RELEASE_NOTES in
makefile. You can use a real release number in the name of the file
(even if release number is alpha or beta). The release script will
rename the file in the archive.

3. make mrprop

4. check in the whole project (I used to do it even for models and papers
but this is not strictly necessary. scope/scope or scope-src should
suffice).

5. tag the whole project with release name with *not* including alpha/beta tags 
and release candidate numbers, but do create a branch (-b). 

cvs tag -b scope-0-15

6. cvs release -d the whole project (not strictly necessary but I found it
good to run the whole process - eliminates some errors)

7. cvs co -r scope-0-15 scope
Do all the development for release in this branch (but merge important changes to trunk).
place the RC numbers in RELEASE in makefile and tag the branch (without -b) with the proper
tag then do:

8. cd scope/scope
9 cross your fingers and:
	make bin-release
	make src-release

10. Test the distrubution. If it works repeat steps for final relase (no
   beta/alpha etc).

Each call creates one tar.gz file in current directory


