|
From: <sv...@va...> - 2005-11-08 20:03:19
|
Author: njn Date: 2005-11-08 20:03:08 +0000 (Tue, 08 Nov 2005) New Revision: 5045 Log: Augment a little. 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-08 19:59:24 UTC (rev 5= 044) +++ trunk/docs/internals/release-HOWTO.txt 2005-11-08 20:03:08 UTC (rev 5= 045) @@ -2,6 +2,13 @@ TODO list when doing a Valgrind release (with release number "X.Y.Z") ------------------------------------------------------------------------= ----- =20 +There are two kinds of releases: + +- Feature releases: X.Y.0, which can include new features. + +- Bug-fix releases: X.Y.[12...], which only include bug fixes. + + First of all: =20 - Tell valgrind-developers you want to do a release. Give a timeframe f= or @@ -40,8 +47,8 @@ include/pub_tool_tooliface.h has been increased since the last release= . =20 =20 -For each release candidate (should do release candidates for big release= s, -bug-fix-only releases might not need one): +For each release candidate (should do release candidates for feature +releases, bug-fix-only releases might not need one): =20 - Do pre-release testing: - Make sure regtests run ok on all platforms of interest. @@ -109,6 +116,9 @@ =20 - Add a new section to docs/internals/X_Y_BUGSTATUS.txt. =20 +- If it was a feature (X.Y.0) release, add an X.Y+1.0 entry to + docs/internals/roadmap.txt. + - Announce the release: - Email valgrind-users, valgrind-developers, and valgrind-announce. - Email Linux Weekly News. |