From: wolf <wolf@0785d39b-7218-0410-832d-ea1e28bc413d>
Date: Thu, 28 Jun 2001 07:38:19 +0000 (+0000)
Subject: Describe the steps to be done for a release
X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f6d1df282f91fc87d8d1d7c914eadb7194e35e0a;p=dealii-svn.git

Describe the steps to be done for a release


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

diff --git a/deal.II/doc/news/release-tasks b/deal.II/doc/news/release-tasks
new file mode 100644
index 0000000000..ed42f46d14
--- /dev/null
+++ b/deal.II/doc/news/release-tasks
@@ -0,0 +1,24 @@
+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:
+    cvs tag all files with the tag Base-x-y
+    cvs tag -r all files with the tag Branch-x-y
+
+- test the branch thoroughly
+
+- adjust news.html. Crosslink changes file. If necessary link an
+  announcement. To 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
+
+- cvs tag all files with Version-x-y-z
+
+- cvs export -r Version-x-y-z and form a tarball of that
+
+- put it onto the web server
+
+- wait overnight
+
+- announce the relase