From fda0ed58d3814f129731135faf12cccd4576bdf4 Mon Sep 17 00:00:00 2001 From: Ben Ramsey Date: Tue, 20 Jul 2021 11:58:08 -0500 Subject: [PATCH] Change release process to create branch at RC1 --- docs/release-process.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/release-process.md b/docs/release-process.md index 8b8746b96ede2..e4a2281fce9a8 100644 --- 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