# 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 below. Note that it is desirable to use an alpha or beta release
# first because it is very hard to corrected certain types of errors in
# release process. So firstly release an alpha.
#
# 2. Write release notes and enter the name in RELEASE_NOTES below. 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 including alpha/beta tags (I
# used to do it even for models and papers but this is not strictly
# necessary. scope/scope or scope-src should suffice).
#
# 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 scope
# 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
#

