[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] maint: update README-release
From: |
Jim Meyering |
Subject: |
[PATCH] maint: update README-release |
Date: |
Mon, 20 Sep 2010 18:36:02 +0200 |
FYI, I noticed that the procedure here was a little out of date.
>From 78fd9c3e1082aa924d6391120f37e803b5368164 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Mon, 20 Sep 2010 18:35:19 +0200
Subject: [PATCH] maint: update README-release
* README-release: Reflect changes in coreutils' version of this file.
---
README-release | 19 ++++++++-----------
1 files changed, 8 insertions(+), 11 deletions(-)
diff --git a/README-release b/README-release
index 0df5ff5..bcb046f 100644
--- a/README-release
+++ b/README-release
@@ -25,7 +25,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 2.6 stable
+ 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 +39,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-grep-X.Y
+ that was just created by that "make" command.
Once all the builds and tests have passed,
@@ -54,14 +55,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.,
+* Announce it on Savannah first, so you can include the preferable
+ savannah.org announcement link in the email message.
- To: address@hidden
- Cc: address@hidden, address@hidden
- Subject: grep-2.6 released [stable]
- Reply-To: address@hidden
-
-* Announce it on Savannah, too:
From here:
https://savannah.gnu.org/projects/grep/
click on the "submit news", then write something like the following:
@@ -69,8 +65,7 @@ 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=grep)
- Subject: grep-2.6 released [stable]
-
+ Subject: grep-X.Y released [stable]
+verbatim+
...paste the announcement here...
-verbatim-
@@ -78,6 +73,8 @@ Once all the builds and tests have passed,
Then go here to approve it:
https://savannah.gnu.org/news/approve.php?group=grep
+* Send the announcement email message.
+
* After each non-alpha release, update the on-line manual accessible via
http://www.gnu.org/software/grep/manual/
--
1.7.3.234.g7bba3
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] maint: update README-release,
Jim Meyering <=