Lines Matching refs:branch
19 The RM for the branch is also responsible for keeping the CI green on
20 ongoing basis between the releases. Check the CI status for your branch
40 - Create a directory for the extension incl. branch and tag structure,
66 4. Checkout the release branch for this release (e.g., PHP-5.4.2) from the main branch.
77 8. If all is right, commit the changes to the release branch with ``git commit -a``.
79 9. Tag the repository release branch with the version, e.g.:
83 in the *main* branch (PHP-5.4 for example) to prepare for the **next** version.
86 Commit the changes to the main branch.
88 11. Push the changes to the main repo, the tag, the main branch and the release branch :
90 ``git push origin {main branch}``
91 ``git push origin {release branch}``
162 1. Checkout your release branch, you should have created when releasing previous RC
167 merge to 5.4, 5.5 etc...). Then you can cherry-pick it in your release branch.
219 highest branch, otherwise you have to do this manually, see point 1.b
332 Forking a new release branch
335 1. One week prior to cutting X.Y.0beta1, warn internals@ that your version's branch
337 Try to be specific about when the branch will be cut.
340 2. Just prior to cutting X.Y.0beta1, create the new branch locally.
341 Add a commit on master after the branch point clearing the NEWS file, and updating
344 Push the new branch and the commit just added to master.
346 3. Immediately notify internals@ of the branch cut and advise the new merging order:
349 4. Update php-web:git.php and wiki.php.net/vcs/gitworkflow to reflect the new branch:
