| njn | af66ea6 | 2005-07-24 23:47:01 +0000 | [diff] [blame^] | 1 | ----------------------------------------------------------------------------- |
| 2 | TODO list when doing a Valgrind release (with release number "X.Y.Z") |
| 3 | ----------------------------------------------------------------------------- |
| 4 | |
| 5 | First of all: |
| 6 | |
| 7 | - Tell valgrind-developers you want to do a release. Give a timeframe for |
| 8 | everyone to check in any final features/bug-fixes they want in the |
| 9 | release. |
| 10 | |
| 11 | - Go over the docs, make sure they're up to date. |
| 12 | |
| 13 | - Update version number and date in docs/xml/vg-entities.xml. (Exact |
| 14 | release date probably won't be known yet, updating it is in the list below |
| 15 | of tasks for the official release.) |
| 16 | |
| 17 | - Write release notes, add to NEWS. Include a list of fixed bugs from |
| 18 | Bugzilla. [[We should decide a defined way of obtaining this list so it's |
| 19 | consistent and so we don't have to work it out anew each time.]] |
| 20 | |
| 21 | - Add X.Y.Z and X.Y.Z.SVN versions to Bugzilla (ask Dirk to do it) |
| 22 | |
| 23 | |
| 24 | For each release candidate (should do release candidates for big releases, |
| 25 | bug-fix-only releases might not need one): |
| 26 | |
| 27 | - Do pre-release testing: |
| 28 | - Make sure regtests run ok on all platforms of interest. |
| 29 | - Make sure Mozilla and OpenOffice run ok on all platforms of interest. |
| 30 | |
| 31 | - Change release number in AC_INIT() in configure.in to "X.Y.Z-rcN", where |
| 32 | 'N' is the release candidate number. |
| 33 | |
| 34 | - Make the tarball ("make dist") and put it on the web somewhere (it doesn't |
| 35 | have to be on valgrind.org if another site is easier). |
| 36 | |
| 37 | - Announce the release: |
| 38 | - Email valgrind-users and valgrind-developers (but not valgrind-announce). |
| 39 | - Make clear it's a release candidate. |
| 40 | - Make sure you tell everyone where to download from. |
| 41 | - Include the release notes in the email (maybe not necessary for release |
| 42 | candidates 2+). |
| 43 | |
| 44 | - Wait 2--3 days for feedback. If bugs appear: |
| 45 | - Fix them. |
| 46 | - Update the bug-fix list in NEWS if necessary. |
| 47 | - Do another release candidate. |
| 48 | |
| 49 | |
| 50 | For the official release: |
| 51 | |
| 52 | - Again, update date in docs/xml/vg-entities.xml for the official release |
| 53 | date. |
| 54 | |
| 55 | - Do pre-release testing: |
| 56 | - Make sure regtests run ok on all platforms of interest. |
| 57 | - Make sure Mozilla and OpenOffice run ok on all platforms of interest. |
| 58 | |
| 59 | - Change release number in AC_INIT() in configure.in to "X.Y.Z". |
| 60 | |
| 61 | - Tag the repository ("VALGRIND_X_Y_Z"). |
| 62 | |
| 63 | - Make the tarball ("make dist"). |
| 64 | |
| 65 | - Update website: |
| 66 | - Put the tarball up. |
| 67 | - Update www.valgrind.org/downloads/source_code.html. |
| 68 | - Add a news item to the front page and also to valgrind.org/info/news.html. |
| 69 | |
| 70 | - Change release number in AC_INIT() in configure.in to "X.Y.Z.SVN", where |
| 71 | X.Y.Z is one more than the release just done. |
| 72 | |
| 73 | - Announce the release: |
| 74 | - Email valgrind-users, valgrind-developers, and valgrind-announce. |
| 75 | - Include the release notes in the email. |
| 76 | |
| 77 | |