Change release process to create branch at RC1

php · Jul 20, 2021 · fda0ed5 · fda0ed5
1 parent 718b675
commit fda0ed5
Showing 1 changed file with 10 additions and 7 deletions.
diff --git a/docs/release-process.md b/docs/release-process.md
@@ -29,8 +29,11 @@ explained at the end of this document in
  3. Ensure that the relevant tests on CI are green.
 
     See:
-      https://ci.appveyor.com/project/php/php-src
-      https://dev.azure.com/phpazuredevops/PHP/
+
+    - https://travis-ci.com/github/php/php-src
+    - https://ci.appveyor.com/project/php/php-src
+    - https://dev.azure.com/phpazuredevops/PHP/
+    - https://cirrus-ci.com/github/php/php-src
 
     It is recommended to do so a couple of days before the packaging day, to
     have enough time to investigate failures, communicate with the authors and
@@ -71,7 +74,7 @@ explained at the end of this document in
     beta. Do not use dashes, you should `#define PHP_VERSION "7.4.22RC1"` and
     not `#define PHP_VERSION "7.4.22-RC1"`.
 
-    When releasing the first release candidate, you must also bump the API
+    ⚠️  When releasing the **first release candidate**, you must also bump the API
     version numbers in `Zend/zend_extensions.h`, `Zend/zend_modules.h`, and
     `main/php.h`. The API versions between the alpha/beta/.0RCx releases can be
     left the same, or bumped as little as possible because PHP extensions will
@@ -363,13 +366,13 @@ explained at the end of this document in
 
 ## Forking a new release branch
 
- 1. One week prior to cutting X.Y.0beta1, warn internals@ that your version's
-    branch is about to be cut, and that PHP-X.Y will be moving into feature
-    freeze. Try to be specific about when the branch will be cut.
+ 1. One week prior to cutting X.Y.0RC1, warn internals@ that your version's
+    branch is about to be cut. Try to be specific about when the branch will
+    be cut.
 
     Example: http://news.php.net/php.internals/99864
 
- 2. Just prior to cutting X.Y.0beta1, create the new branch locally.
+ 2. Just prior to cutting X.Y.0RC1, create the new branch locally.
 
     Add a commit on master after the branch point clearing the `NEWS`,
     `UPGRADING` and `UPGRADING.INTERNALS` files, updating the version in