Assign numbers

git-svn-id: https://svn.dealii.org/trunk@5378 0785d39b-7218-0410-832d-ea1e28bc413d

diff --git a/deal.II/doc/RELEASE/tasks b/deal.II/doc/RELEASE/tasks
index db95c534d55e2dba561e6024676b0905a54b1ba7..971cf1cc894b33daf389f2a97a8c00c078ecef1f 100644 (file)
--- a/deal.II/doc/RELEASE/tasks
+++ b/deal.II/doc/RELEASE/tasks
@@ -1,35 +1,35 @@
 This file is internal information only. It lists the steps to be done
 when a new release shall be issued:
 
-- if a x.y.0 release, create a branch:
+1/ if a x.y.0 release, create a branch:
     cvs tag all files with the tag Base-x-y
     cvs tag -r all files with the tag Branch-x-y
 
-- tell your friends to tag their programs
+2/ tell your friends to tag their programs
 
-- change the content of the `Version' file on both HEAD and branch
+3/ change the content of the `Version' file on both HEAD and branch
 
-- test the branch thoroughly
+4/ test the branch thoroughly
 
-- rename the changes file and create a new one for the next release
+5/ rename the changes file and create a new one for the next release
 
-- adjust news.html. Crosslink changes file. If necessary link an
+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.
 
-- adjust download.html on both HEAD and branch.
+7/ adjust download.html on both HEAD and branch.
 
-- run `make validate-xrefs' on the branch to check that the changes
+8/ run `make validate-xrefs' on the branch to check that the changes
   do not point to nirvana
 
-- cvs tag all files with Version-x-y-z
+10/ cvs tag all files with Version-x-y-z
 
-- tell your friends to tag their programs
+11/ tell your friends to tag their programs
 
-- cvs export -r Version-x-y-z and form a tarball of that
+12/ cvs export -r Version-x-y-z and form a tarball of that
 
-- put it on the web server
+13/ put it on the web server
 
-- wait overnight
+14/ wait overnight
 
-- announce the release
+15/ announce the release