com php-src: Add notes for cutting release branches: README.RELEASE_PROCESS

Commit: 3a8fb765735b051e8dce0bb202ea611ed7ac0ada Author: Sara Golemon <pollita@php.net> Tue, 18 Jul 2017 18:26:48 -0400 Parents: 39337a6d80e453d3324a79881c66dfcf6070f12e Branches: master Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=3a8fb765735b051e8dce0bb202ea611ed7ac0ada Log: Add notes for cutting release branches Changed paths: M README.RELEASE_PROCESS Diff: diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index 112d503..c735d5e 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -327,6 +327,28 @@ Please make sure that the mail to php-announce@ is its own completely separate e This is to make sure that replies to the announcement on php-general@ or internals@ will not accidentally hit the php-announce@ mailinglist. +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. + Example: http://news.php.net/php.internals/99864 + +2. Just prior to cutting X.Y.0beta1, create the new branch locally. + Add a commit on master after the branch point clearing the NEWS file, and updating + main/php_versions.h and Zend/zend.h to update versions. + Example: https://github.com/php/php-src/commit/5230541ef59e0637d5522293a7d099bf18ce6af3 + Push the new branch and the commit just added to master. + +3. Immediately notify internals@ of the branch cut and advise the new merging order: + Example: http://news.php.net/php.internals/99903 + +4. Update php-web:git.php and wiki.php.net/vcs/gitworkflow to reflect the new branch: + Example: https://github.com/php/web-php/commit/74bcad4c770d95f21b7fbeeedbd76d943bb83f23 + +5. Notify nlopess@ to add PHP_X_Y tag to gcov.php.net + New Release Manager Checklist -----------------------------