1/ if a x.y.0 release, create a branch:
call common/scripts/cvs-create-branch <x> <y>
- from the deal home directory
2/ cvs update -r Branch-<x>-<y>
or
cvs checkout -r Branch-<x>-<y> deal.II
+3/ change the content of the `Version' file on both HEAD and branch
+
+4/ test the branch thoroughly
+
+5/ rename the changes file and create a new one for the next release
+
+6/ adjust news.html. Crosslink changes file. If necessary link an
+ announcement. Do these things on both HEAD and branch. Be sure to
+ have the changes file on both HEAD and branch.
+
+7/ adjust download.html on both HEAD and branch.
+
+8/ run `make validate-xrefs' on the branch to check that the changes
+ do not point to nirvana
+
+ from the deal home directory
+
10/ cvs tag all files with Version-x-y-z
11/ tell your friends to tag their programs