philip                                   Mon, 30 May 2011 23:26:33 +0000

Revision: http://svn.php.net/viewvc?view=revision&revision=311614

Log:
Updated qa-release.php notes as per the new qa-release.php syntax

Changed paths:
    U   php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS
    U   php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS
    U   php/php-src/trunk/README.RELEASE_PROCESS

Modified: php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS
===================================================================
--- php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-05-30 21:58:30 UTC 
(rev 311613)
+++ php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-05-30 23:26:33 UTC 
(rev 311614)
@@ -100,17 +100,15 @@

 ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod 
moderator-email-address``

-3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty 
lines).
+3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate 
information.
+   See the documentation within release-qa.php for more information, but all 
releases
+   and RCs are configured here. Only $QA_RELEASES needs to be edited.

-4. Update in ``web/qa/trunk/include/release-qa.php`` constants with the new RC 
and
-commit this.
+   Example: When rolling an RC, set the 'rc' with appropriate information for 
the
+   given version.

- a. ``$BUILD_TEST_RELEASES`` = array("4.4.7RC1", "5.2.2RC1")
+   Note: Remember to update the MD5 checksum information.

- b. ``$CURRENT_QA_RELEASE_4`` = "4.4.7RC1" (``$CURRENT_QA_RELEASE_5`` for PHP5)
-
- c. ``$RELEASE_PROCESS`` = array(4 => true, 5 => true)
-
 1. Update in ``php-bugs/trunk/include/functions.inc`` the 
``show_version_option``
 function to include the new RC and commit.

@@ -244,14 +242,12 @@

 11. Update ``qaweb/include/release-qa.php``

- a. Update the $BUILD_TEST_RELEASES array with the release name
+ - Update $QA_RELEASES with the appropriate information, which means bumping
+   the version number to an upcoming version.

- b. Update $RELEASE_PROCESS array (set to false)
+   Example: If PHP 5.3.7 is being released, then PHP 5.3.8 is the next QA 
version,
+   so replace 5.3.7 with 5.3.8 within $QA_RELEASES.

-  I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false
-
-  II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false
-
 Re-releasing the same version (or -pl)
 --------------------------------------


Modified: php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS
===================================================================
--- php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2011-05-30 21:58:30 UTC 
(rev 311613)
+++ php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2011-05-30 23:26:33 UTC 
(rev 311614)
@@ -104,17 +104,16 @@

 ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod 
moderator-email-address``

-3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty 
lines, ordered by filename, odler version number first, .bz2 before .gz).
+3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate 
information.
+   See the documentation within release-qa.php for more information, but all 
releases
+   and RCs are configured here. Only $QA_RELEASES needs to be edited.

-4. Update in ``web/qa/trunk/include/release-qa.php`` constants with the new RC 
and
-commit this.
+   Example: When rolling an RC, set the 'rc' with appropriate information for 
the
+   given version.

- a. ``$BUILD_TEST_RELEASES`` = array("4.4.7RC1", "5.2.2RC1")
+   Note: Remember to update the MD5 checksum information.

- b. ``$CURRENT_QA_RELEASE_4`` = "4.4.7RC1" (``$CURRENT_QA_RELEASE_5`` for PHP5)

- c. ``$RELEASE_PROCESS`` = array(4 => true, 5 => true)
-
 1. Update in ``web/php-bugs/trunk/include/php_versions.php`` to include the 
new RC and commit.

 2. Update ``web/php/trunk/include/version.inc`` (x=major version number)
@@ -247,14 +246,12 @@

 11. Update ``qaweb/include/release-qa.php``

- a. Update the $BUILD_TEST_RELEASES array with the release name
+ - Update $QA_RELEASES with the appropriate information, which means bumping
+   the version number to an upcoming version.

- b. Update $RELEASE_PROCESS array (set to false)
+   Example: If PHP 5.3.7 is being released, then PHP 5.3.8 is the next QA 
version,
+   so replace 5.3.7 with 5.3.8 within $QA_RELEASES.

-  I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false
-
-  II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false
-
 Re-releasing the same version (or -pl)
 --------------------------------------


Modified: php/php-src/trunk/README.RELEASE_PROCESS
===================================================================
--- php/php-src/trunk/README.RELEASE_PROCESS    2011-05-30 21:58:30 UTC (rev 
311613)
+++ php/php-src/trunk/README.RELEASE_PROCESS    2011-05-30 23:26:33 UTC (rev 
311614)
@@ -104,17 +104,15 @@

 ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod 
moderator-email-address``

-3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty 
lines, ordered by filename, odler version number first, .bz2 before .gz).
+3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate 
information.
+   See the documentation within release-qa.php for more information, but all 
releases
+   and RCs are configured here. Only $QA_RELEASES needs to be edited.

-4. Update in ``web/qa/trunk/include/release-qa.php`` constants with the new RC 
and
-commit this.
+   Example: When rolling an RC, set the 'rc' with appropriate information for 
the
+   given version.

- a. ``$BUILD_TEST_RELEASES`` = array("4.4.7RC1", "5.2.2RC1")
+   Note: Remember to update the MD5 checksum information.

- b. ``$CURRENT_QA_RELEASE_4`` = "4.4.7RC1" (``$CURRENT_QA_RELEASE_5`` for PHP5)
-
- c. ``$RELEASE_PROCESS`` = array(4 => true, 5 => true)
-
 1. Update in ``web/php-bugs/trunk/include/php_versions.php`` to include the 
new RC and commit.

 2. Update ``web/php/trunk/include/version.inc`` (x=major version number)
@@ -247,14 +245,12 @@

 11. Update ``qaweb/include/release-qa.php``

- a. Update the $BUILD_TEST_RELEASES array with the release name
+ - Update $QA_RELEASES with the appropriate information, which means bumping
+   the version number to an upcoming version.

- b. Update $RELEASE_PROCESS array (set to false)
+   Example: If PHP 5.3.7 is being released, then PHP 5.3.8 is the next QA 
version,
+   so replace 5.3.7 with 5.3.8 within $QA_RELEASES.

-  I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false
-
-  II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false
-
 Re-releasing the same version (or -pl)
 --------------------------------------


-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to