[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

grep branch, master, updated. v2.7-3-g78fd9c3

From: Jim Meyering
Subject: grep branch, master, updated. v2.7-3-g78fd9c3
Date: Mon, 20 Sep 2010 16:35:22 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".

The branch, master has been updated
       via  78fd9c3e1082aa924d6391120f37e803b5368164 (commit)
      from  24d9aefd4be68f06b8c6c74b07e51736958d24fd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------

commit 78fd9c3e1082aa924d6391120f37e803b5368164
Author: Jim Meyering <address@hidden>
Date:   Mon Sep 20 18:35:19 2010 +0200

    maint: update README-release
    * README-release: Reflect changes in coreutils' version of this file.

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
+ 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:
   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:
-    Subject: grep-2.6 released [stable]
+    Subject: grep-X.Y released [stable]
     ...paste the announcement here...
@@ -78,6 +73,8 @@ Once all the builds and tests have passed,
   Then go here to approve it:
+* Send the announcement email message.
 * After each non-alpha release, update the on-line manual accessible via


Summary of changes:
 README-release |   19 ++++++++-----------
 1 files changed, 8 insertions(+), 11 deletions(-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]