@@ -29,8 +29,11 @@ explained at the end of this document in
29
29
3 . Ensure that the relevant tests on CI are green.
30
30
31
31
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
34
37
35
38
It is recommended to do so a couple of days before the packaging day, to
36
39
have enough time to investigate failures, communicate with the authors and
@@ -71,7 +74,7 @@ explained at the end of this document in
71
74
beta. Do not use dashes, you should ` #define PHP_VERSION "7.4.22RC1" ` and
72
75
not ` #define PHP_VERSION "7.4.22-RC1" ` .
73
76
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
75
78
version numbers in ` Zend/zend_extensions.h ` , ` Zend/zend_modules.h ` , and
76
79
` main/php.h ` . The API versions between the alpha/beta/.0RCx releases can be
77
80
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
363
366
364
367
# # Forking a new release branch
365
368
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.
369
372
370
373
Example: http://news.php.net/php.internals/99864
371
374
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.
373
376
374
377
Add a commit on master after the branch point clearing the `NEWS`,
375
378
`UPGRADING` and `UPGRADING.INTERNALS` files, updating the version in
0 commit comments