@@ -29,8 +29,11 @@ explained at the end of this document in
2929 3 . Ensure that the relevant tests on CI are green.
3030
3131 See:
32- https://ci.appveyor.com/project/php/php-src
33- https://dev.azure.com/phpazuredevops/PHP/
32+
33+ - https://travis-ci.com/github/php/php-src
34+ - https://ci.appveyor.com/project/php/php-src
35+ - https://dev.azure.com/phpazuredevops/PHP/
36+ - https://cirrus-ci.com/github/php/php-src
3437
3538 It is recommended to do so a couple of days before the packaging day, to
3639 have enough time to investigate failures, communicate with the authors and
@@ -71,7 +74,7 @@ explained at the end of this document in
7174 beta. Do not use dashes, you should ` #define PHP_VERSION "7.4.22RC1" ` and
7275 not ` #define PHP_VERSION "7.4.22-RC1" ` .
7376
74- When releasing the first release candidate, you must also bump the API
77+ ⚠️ When releasing the ** first release candidate** , you must also bump the API
7578 version numbers in ` Zend/zend_extensions.h ` , ` Zend/zend_modules.h ` , and
7679 ` main/php.h ` . The API versions between the alpha/beta/.0RCx releases can be
7780 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
363366
364367# # Forking a new release branch
365368
366- 1. One week prior to cutting X.Y.0beta1 , warn internals@ that your version' s
367- branch is about to be cut, and that PHP-X.Y will be moving into feature
368- freeze. Try to be specific about when the branch will be cut.
369+ 1. One week prior to cutting X.Y.0RC1 , warn internals@ that your version' s
370+ branch is about to be cut. Try to be specific about when the branch will
371+ be cut.
369372
370373 Example: http://news.php.net/php.internals/99864
371374
372- 2. Just prior to cutting X.Y.0beta1 , create the new branch locally.
375+ 2. Just prior to cutting X.Y.0RC1 , create the new branch locally.
373376
374377 Add a commit on master after the branch point clearing the `NEWS`,
375378 `UPGRADING` and `UPGRADING.INTERNALS` files, updating the version in
0 commit comments