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 an 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}``
165 1. Checkout your release branch, you should have created when releasing previous RC
170 merge to 5.4, 5.5 etc...). Then you can cherry-pick it in your release branch.
217 highest branch, otherwise you have to do this manually, see point 1.b
