|
From: <sv...@va...> - 2005-11-15 15:27:19
|
Author: njn
Date: 2005-11-15 15:27:06 +0000 (Tue, 15 Nov 2005)
New Revision: 5133
Log:
More detail about pre-release testing.
Modified:
trunk/docs/internals/release-HOWTO.txt
Modified: trunk/docs/internals/release-HOWTO.txt
=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.txt 2005-11-15 02:24:57 UTC (rev 5=
132)
+++ trunk/docs/internals/release-HOWTO.txt 2005-11-15 15:27:06 UTC (rev 5=
133)
@@ -13,7 +13,7 @@
=20
- Tell valgrind-developers you want to do a release. Give a timeframe f=
or
everyone to check in any final features/bug-fixes they want in the
- release.
+ release. (Especially Josef Weidendorfer for Callgrind.)
=20
- Go over the docs, make sure they're up to date.
=20
@@ -51,9 +51,39 @@
releases, bug-fix-only releases might not need one):
=20
- Do pre-release testing:
- - Make sure regtests run ok on all platforms of interest.
- - Make sure Mozilla and OpenOffice run ok on all platforms of interest=
.
=20
+ * Check it builds and regtests on a vanilla gcc-2.96 / RedHat 7.3 dist=
ro.
+ Also check that callgrind builds/installs alongside it OK.
+
+ * Check standard build and regtest on the following cpus:
+ x86, sse2 (P4)
+ x86, sse1 (PIII)
+ x86, no sse (eg older VIA C3s, or perhaps even Pentium-MMX)
+ amd64
+ ppc32, altivec
+ ppc32, no altivec (eg old iMac G3s)
+
+ * Check that the regression tests work with --sanity-level=3D4 on all
+ platforms.
+
+ * Check valgrind-listener works on all archs, also connecting to it
+ from all archs.
+
+ * Check memcheck can run all the insn-set tests. The testsuite
+ only runs those on 'none', but memcheck looks at all primops, and I'=
ve
+ been caught out by this before. Basically all the programs in
+ none/tests/{x86,amd64,ppc32}.
+
+ * Check XML output is still readable by Valkyrie and vk_logmerge tools
+
+ * Test with large applications (firefox and OOo 2.0) on all platforms.
+
+ * Run regression tests from gsl-1.6 on all platforms. This is a good,
+ thorough test of FP. Easy, using the scripts auxprogs/gsl16test.
+
+ * Check that a tarball build of callgrind is buildable/installable
+ against a from-tarball build of valgrind.
+
- Change release number in AC_INIT() in configure.in to "X.Y.Z-rcN", whe=
re
'N' is the release candidate number.
=20
|