From: Guido Kanschat Date: Tue, 28 Dec 2004 17:41:38 +0000 (+0000) Subject: What I did for 5.1.0 X-Git-Tag: v8.0.0~14626 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8c6d4e8e489def5961a35608af5aa80c0bb9d576;p=dealii.git What I did for 5.1.0 git-svn-id: https://svn.dealii.org/trunk@9864 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/RELEASE/tasks b/deal.II/doc/RELEASE/tasks index e058f69f13..3832341473 100644 --- a/deal.II/doc/RELEASE/tasks +++ b/deal.II/doc/RELEASE/tasks @@ -1,7 +1,11 @@ This file is internal information only. It lists the steps to be done when a new release shall be issued: -0/ cvs update -d -P +0/ + cvs update -d -P + make all + cd tests ; make all ; cd .. + cd examples ; make all ; cd .. *** Caveat: for a minor version x.y.Z, *** 1-3 must be performed on Branch-x-y @@ -13,7 +17,7 @@ when a new release shall be issued: used to show changes after last release. Crosslink changes file. If necessary link an announcement. -3/ obsolete +3/ Commit the changes of step 2! 4/ if a x.y.0 release, create a branch: call common/scripts/cvs-create-branch @@ -29,7 +33,7 @@ when a new release shall be issued: 7/ test the branch thoroughly: make distclean (if applicable) - ./configure + ./configure --with-umfpack make all cd tests make all