From fbd82a0a25ff15b9496eab733cef4ba2bf263176 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Wed, 18 Jan 2012 14:43:12 +0100 Subject: [PATCH] Tweak release procedure --- bacula/release/ReleaseProcedure.txt | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/bacula/release/ReleaseProcedure.txt b/bacula/release/ReleaseProcedure.txt index 0431733eca..b304fb2093 100644 --- a/bacula/release/ReleaseProcedure.txt +++ b/bacula/release/ReleaseProcedure.txt @@ -4,6 +4,7 @@ These are the steps to complete for making a new release. 1. Ensure that the previous release had a tag pushed. If not create one at the prior release point and push it to the repos. + git push tag 2. Update the ChangeLog using release/git2changelog.pl Release-5.2.x..HEAD >1 @@ -53,15 +54,18 @@ These are the steps to complete for making a new release. 16. push the tags (once pushed they can be corrected but it is more complicated than simply re-running the ./makeall script) + ./pushtags which does in all repos + + git push tag 17. Upload the release files to Source Forge. 18. Update the release version and date on the main bacula.org page -19. Update the link to the release version in the "Current Release" - in the menu (inc/header.php). - -20. Update the news item to announce the release. +19. Update the news item to announce the release. -21. Send the release announcement to the users, devel, and announce +20. Send the release announcement to the users, devel, and announce mailing lists. + +21. Update the link to the release version in the "Current Release" + in the menu (inc/header.php). -- 2.39.5