wibble++
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4263 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/docs/internals/release-HOWTO b/docs/internals/release-HOWTO
index 44533b8..6e19640 100644
--- a/docs/internals/release-HOWTO
+++ b/docs/internals/release-HOWTO
@@ -38,6 +38,11 @@
- Make the tarball ("make dist") and put it on the web somewhere (it doesn't
have to be on valgrind.org if another site is easier).
+- Ensure the tarball builds, runs, regtests on the platforms of interest.
+ However redundant this seems, sometimes it can be that a from-the-repo
+ build works whereas a from-the-tarball one doesn't, usually due to some
+ trivial installation problem.
+
- Announce the release:
- Email valgrind-users and valgrind-developers (but not valgrind-announce).
- Make clear it's a release candidate.
@@ -62,9 +67,12 @@
- Change release number in AC_INIT() in configure.in to "X.Y.Z".
-- Tag the repository ("VALGRIND_X_Y_Z").
-
- Make the tarball ("make dist").
+
+- Check tarball builds, installs, regtests on platforms of interest.
+ If not, fix and repeat until success.
+
+- Tag the repository ("VALGRIND_X_Y_Z").
- Update website:
- Put the tarball up.
@@ -76,7 +84,8 @@
X.Y.Z is one more than the release just done.
- Announce the release:
- - Email valgrind-users, valgrind-developers, and valgrind-announce.
+ - Email valgrind-users, valgrind-developers, and valgrind-announce.
+ - Email Linux Weekly News.
- Include the release notes in the email.
-
+- Go on holiday.