Skip to content
Browse files

- made it clear which steps are relevant for RCs only

  • Loading branch information...
1 parent 4222232 commit 0909b1b0e13cc257e8fa0b523a601275e8e214be Lukas Smith committed Sep 3, 2008
Showing with 5 additions and 4 deletions.
@@ -78,15 +78,16 @@ f.e.
( so that Windows binaries can be created. Once
those are made, they should be placed into the same directory as the source snapshots.
-Getting the non stable release announced
+Getting the non stable release (alpha/beta/RC) announced
1. Send an email (see example here:
**To** ```` and ```` lists
pointing out "the location of the release" and "the possible release date of
either the next RC, or the final release".
-2. Send an email (see example here **To**
+2. Only for an RC release also send an email
+(see example here **To**
```` and **CC** ````.
This email is to notify the selected projects about a new RC so that they can
make sure their projects keep working. Make sure that you have been setup
@@ -97,7 +98,7 @@ Derick) run the following commands for you:
``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address``
-3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``.
+3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt`` (no empty lines).
4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and
commit this.

0 comments on commit 0909b1b

Please sign in to comment.
Something went wrong with that request. Please try again.