[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] doc: update release procedure
From: |
Jim Meyering |
Subject: |
[PATCH] doc: update release procedure |
Date: |
Fri, 18 Mar 2011 10:18:37 +0100 |
FYI, I've pushed this:
>From e37e833b21616e484aa81d739869fc6801d5bb0c Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Fri, 18 Mar 2011 10:18:01 +0100
Subject: [PATCH] doc: update release procedure
* README-release: Resync from coreutils' file by the same name.
---
README-release | 30 +++++++++++++++++++-----------
1 files changed, 19 insertions(+), 11 deletions(-)
diff --git a/README-release b/README-release
index f336ac8..3b26e5a 100644
--- a/README-release
+++ b/README-release
@@ -13,6 +13,11 @@ Here are most of the steps we (maintainers) follow when
making a release.
* Ensure that you're on "master" with no uncommitted diffs.
This should produce no output: git checkout master; git diff
+* Ensure that you've pushed all changes that belong in the release
+ and that the NixOS/Hydra autobuilder is reporting all is well:
+
+ http://hydra.nixos.org/jobset/gnu/gzip-master
+
* Run bootstrap one last time. This downloads any new translations:
./bootstrap
@@ -25,7 +30,7 @@ Here are most of the steps we (maintainers) follow when
making a release.
* Set the date, version number, and release type [stable/alpha/beta] on
line 3 of NEWS, commit that, and tag the release by running e.g.,
- build-aux/do-release-commit-and-tag 8.1 beta
+ build-aux/do-release-commit-and-tag X.Y stable
* Run the following to create release tarballs. Your choice selects the
corresponding upload-to destination in the emitted gnupload command.
@@ -39,7 +44,8 @@ Here are most of the steps we (maintainers) follow when
making a release.
it builds and passes all tests.
* While that's happening, write the release announcement that you will
- soon post.
+ soon post. Start with the template, $HOME/announce-gzip-X.Y
+ that was just created by that "make" command.
Once all the builds and tests have passed,
@@ -54,13 +60,9 @@ Once all the builds and tests have passed,
v=$(cat .prev-version)
git push origin master tag v$v
-* Send the gpg-signed announcement mail, e.g.,
-
- To: address@hidden
- Cc: address@hidden, address@hidden
- Subject: gzip-1.3.13 released [stable]
+* Announce it on Savannah first, so you can include the preferable
+ savannah.org announcement link in the email message.
-* Announce it on Savannah, too:
From here:
https://savannah.gnu.org/projects/gzip/
click on the "submit news", then write something like the following:
@@ -68,13 +70,19 @@ Once all the builds and tests have passed,
the Main -> "Select Features" menu item, or via this link:
https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=gzip)
- Subject: gzip-1.3.13 released [stable]
- The announcement is here:
- http://article.gmane.org/gmane.comp.gnu.gzip.bugs/258
+ Subject: gzip-X.Y released [stable]
+ +verbatim+
+ ...paste the announcement here...
+ -verbatim-
Then go here to approve it:
https://savannah.gnu.org/news/approve.php?group=gzip
+* Send the announcement email message.
+
+* Approve the announcement here:
+ http://lists.gnu.org/mailman/admindb/gzip-announce
+
* After each non-alpha release, update the on-line manual accessible via
http://www.gnu.org/software/gzip/manual/
--
1.7.4.1.494.g5ddab
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] doc: update release procedure,
Jim Meyering <=