|
From: <sv...@va...> - 2005-07-25 23:50:23
|
Author: sewardj
Date: 2005-07-26 00:50:22 +0100 (Tue, 26 Jul 2005)
New Revision: 4263
Log:
wibble++
Modified:
trunk/docs/internals/release-HOWTO
Modified: trunk/docs/internals/release-HOWTO
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/internals/release-HOWTO 2005-07-25 23:36:58 UTC (rev 4262)
+++ trunk/docs/internals/release-HOWTO 2005-07-25 23:50:22 UTC (rev 4263)
@@ -38,6 +38,11 @@
- Make the tarball ("make dist") and put it on the web somewhere (it doe=
sn't
have to be on valgrind.org if another site is easier).
=20
+- 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 som=
e
+ trivial installation problem.
+
- Announce the release:
- Email valgrind-users and valgrind-developers (but not valgrind-annou=
nce). =20
- Make clear it's a release candidate. =20
@@ -62,9 +67,12 @@
=20
- Change release number in AC_INIT() in configure.in to "X.Y.Z".
=20
+- 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").
-
-- Make the tarball ("make dist").
=20
- Update website:=20
- Put the tarball up.
@@ -76,7 +84,8 @@
X.Y.Z is one more than the release just done.
=20
- Announce the release:
- - Email valgrind-users, valgrind-developers, and valgrind-announce. =20
+ - Email valgrind-users, valgrind-developers, and valgrind-announce.
+ - Email Linux Weekly News.
- Include the release notes in the email.
=20
-
+- Go on holiday.
|