Lines Matching refs:release

2 TODO list when doing a Valgrind release (with release number "X.Y.Z")
14 - Tell valgrind-developers you want to do a release.  Give a timeframe for
16   release.
21   release date probably won't be known yet, updating it is in the list below
22   of tasks for the official release.)
25   for the release.  (include/valgrind.h)
27 - Write release notes, add to NEWS.  Include a list of fixed bugs from
37   at the previous release.  Work backwards through this list until
43   Suggestion for next release: when a bug is fixed, update NEWS
63 For each release candidate (should do release candidates for feature
68 - Do pre-release testing:
108 - Change release number in AC_INIT() in configure.in to "X.Y.Z-rcN", where
109   'N' is the release candidate number.
122 - Announce the release:
124   - Make clear it's a release candidate.  
126   - Include the release notes in the email (maybe not necessary for release
132   - Do another release candidate.
135 For the official release:
137 - Again, update date in docs/xml/vg-entities.xml for the official release
140 - Do pre-release testing:
144 - Change release number in AC_INIT() in configure.in to "X.Y.Z".
154   If it's a X.Y.0 release, make "VALGRIND_X_Y_BRANCH" and "VEX_X_Y_BRANCH"
155   branches too.  Useful examples (X.Y.0 major release):
173   (X.Y.Z minor release):
193     Include a link to the release notes.  Possibly remove any old release
195   - Update the "release-date" and "release-version" in php/.htconfx.
198 - Change release number in AC_INIT() in configure.in to "X.Y.Z.SVN", where
199   X.Y.Z is one more than the release just done.
201 - Make sure the release notes are present in the NEWS file on the trunk and
204 - Announce the release:
207   - Include the release notes in the email.