[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] maint: use gnulib's new readme-release module
From: |
Jim Meyering |
Subject: |
[PATCH] maint: use gnulib's new readme-release module |
Date: |
Sat, 07 May 2011 16:31:29 +0200 |
FYI,
>From ed23dd209be44d0a13eb0a2816db45b0e3304a28 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 7 May 2011 15:52:30 +0200
Subject: [PATCH] maint: use gnulib's new readme-release module
* bootstrap.conf (gnulib_modules): Add readme-release.
(bootstrap_epilogue): Add the recommended perl one-liner.
* README-release: Remove file; it is now generated from gnulib.
* .gitignore: Add it.
* gnulib: Update submodule to latest.
---
.gitignore | 1 +
README-release | 89 --------------------------------------------------------
bootstrap.conf | 2 +
gnulib | 2 +-
4 files changed, 4 insertions(+), 90 deletions(-)
delete mode 100644 README-release
diff --git a/.gitignore b/.gitignore
index 18f58aa..04320a6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,6 +12,7 @@
/GNUmakefile
/ID
/INSTALL
+/README-release
/aclocal.m4
/autom4te.cache
/build-aux/compile
diff --git a/README-release b/README-release
deleted file mode 100644
index 29a0edb..0000000
--- a/README-release
+++ /dev/null
@@ -1,89 +0,0 @@
-Here are most of the steps we (maintainers) follow when making a release.
-
-* start from a clean, up-to-date git directory.
-
- git checkout master; git pull
-
-* Run ./configure && make maintainer-clean
-
-* Ensure that the desired versions of autoconf, automake, etc.
- are in your PATH. See the buildreq list in bootstrap.conf for
- the complete list.
-
-* 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/grep-master
-
-* Run bootstrap one last time. This downloads any new translations:
-
- ./bootstrap
-
-* Pre-release testing:
- Ensure that make check syntax-check succeeds.
-
-* Run "make distcheck"
-
-* 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 X.Y stable
-
-* Run the following to create release tarballs. Your choice selects the
- corresponding upload-to destination in the emitted gnupload command.
- The different destinations are specified in cfg.mk. See the definitions
- of gnu_ftp_host-{alpha,beta,stable}.
-
- # "TYPE" must be stable, beta or alpha
- make TYPE
-
-* Test the tarball. copy it to a few odd-ball systems and ensure that
- it builds and passes all tests.
-
-* While that's happening, write the release announcement that you will
- 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,
-
-* Run the gnupload command that was suggested by your "make stable" run above.
-
-* Wait a few minutes (maybe up to 30?) and then use the release URLs to
- download all tarball/signature pairs and use gpg --verify to ensure
- that they're all valid.
-
-* Push the NEWS-updating changes and the new tag:
-
- v=$(cat .prev-version)
- git push origin master tag v$v
-
-* Announce it on Savannah first, so you can include the preferable
- savannah.org announcement link in the email message.
-
- From here:
- https://savannah.gnu.org/projects/grep/
- click on the "submit news", then write something like the following:
- (If there is no such button, then enable "News" for the project via
- the Main -> "Select Features" menu item, or via this link:
- https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=grep)
-
- Subject: grep-X.Y released [stable]
- +verbatim+
- ...paste the announcement here...
- -verbatim-
-
- 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/
-
- by running this:
-
- build-aux/gnu-web-doc-update
diff --git a/bootstrap.conf b/bootstrap.conf
index 402ffcb..2cd1d9a 100644
--- a/bootstrap.conf
+++ b/bootstrap.conf
@@ -59,6 +59,7 @@ open
progname
propername
quotearg
+readme-release
realloc-gnu
regex
ssize_t
@@ -152,4 +153,5 @@ bootstrap_epilogue()
m=gnulib-tests/gnulib.mk
sed 's,\.\./\.\.,..,g' $m > $m-t
mv -f $m-t $m
+ perl -pi -e "s/address@hidden@/$package/g" README-release
}
diff --git a/gnulib b/gnulib
index 8585ce2..c1a8825 160000
--- a/gnulib
+++ b/gnulib
@@ -1 +1 @@
-Subproject commit 8585ce2ff5698c650ba5d5e3bb99763654ad62e8
+Subproject commit c1a8825410ad58e8344bdb202b2559935179e513
--
1.7.5.1.299.g6e1e4
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] maint: use gnulib's new readme-release module,
Jim Meyering <=