aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlloyd <[email protected]>2014-01-31 22:34:05 +0000
committerlloyd <[email protected]>2014-01-31 22:34:05 +0000
commit43b79ef586143d93a6843f8e9a34f774103f46b3 (patch)
treee055a9b5c325d2b9aa9bf41fe9809ff364ae0cc5
parentda27504c4477837bfbe92cf6d510fb327c2e8c4b (diff)
Simplify
-rw-r--r--doc/dev/release_process.rst12
1 files changed, 1 insertions, 11 deletions
diff --git a/doc/dev/release_process.rst b/doc/dev/release_process.rst
index cf7ba44fc..b7cc1655d 100644
--- a/doc/dev/release_process.rst
+++ b/doc/dev/release_process.rst
@@ -13,7 +13,7 @@ Confirm that the release notes under ``doc/relnotes`` are accurate and
complete and that the version number in ``botan_version.py`` is
correct. Update the release date in the release notes and change the
entry for the appropriate branch in ``doc/download.rst`` to point to
-the new release.
+the new release. Add the new release to ``relnotes/index.rst``.
Check in these changes (alone, with no other modifications) with a
checkin message along the lines of "Update for X.Y.Z release", then
@@ -75,13 +75,3 @@ Announce The Release
Send an email to the announce and devel mailing lists noting that a
new release is available.
-
-Post Release Process
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Immediately after the new release is created, increment the version
-number in ``botan_version.py`` and add a new release notes file for
-the next release, including a new entry in ``doc/relnotes/index.rst``.
-
-Use "Not Yet Released" as the placeholder for the release date. Use
-checkin message "Bump for X.Y.Z".