From: Nicholas Nethercote Date: Sat, 27 Jan 2007 02:05:38 +0000 (+0000) Subject: update X-Git-Tag: svn/VALGRIND_3_3_0~404 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=323ba9fa25ef512ce6835aa76a4f8b0762db9fbc;p=thirdparty%2Fvalgrind.git update git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6555 --- diff --git a/docs/internals/release-HOWTO.txt b/docs/internals/release-HOWTO.txt index 39b9ae62ac..096d6dc390 100644 --- a/docs/internals/release-HOWTO.txt +++ b/docs/internals/release-HOWTO.txt @@ -50,6 +50,10 @@ First of all: For each release candidate (should do release candidates for feature releases, bug-fix-only releases might not need one): +- Build. Don't forget to rebuild the Vex header file that specifies which + version of Vex is being used (so that it matches that mentioned in the final + release notes). [This was forgotten for 3.2.2.] + - Do pre-release testing: * Check it builds and regtests on a vanilla gcc-2.96 / RedHat 7.3 distro.