From 2f5a6212154eb5930544902e840416dfb6376e59 Mon Sep 17 00:00:00 2001 From: wolf Date: Mon, 3 Jun 2002 12:30:39 +0000 Subject: [PATCH] tasks-3.3 is clearly outdated. git-svn-id: https://svn.dealii.org/trunk@5971 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/RELEASE/tasks-3.3 | 35 ----------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 deal.II/doc/RELEASE/tasks-3.3 diff --git a/deal.II/doc/RELEASE/tasks-3.3 b/deal.II/doc/RELEASE/tasks-3.3 deleted file mode 100644 index 971cf1cc89..0000000000 --- a/deal.II/doc/RELEASE/tasks-3.3 +++ /dev/null @@ -1,35 +0,0 @@ -This file is internal information only. It lists the steps to be done -when a new release shall be issued: - -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 - -2/ tell your friends to tag their programs - -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 - -10/ cvs tag all files with Version-x-y-z - -11/ tell your friends to tag their programs - -12/ cvs export -r Version-x-y-z and form a tarball of that - -13/ put it on the web server - -14/ wait overnight - -15/ announce the release -- 2.39.5