Lines Matching refs:branch
6 The release schedule for their branch is available on a Wiki page, for example
41 Check the CI status for your branch periodically and resolve the failures ASAP.
68 3. Checkout the release branch for this release (e.g., PHP-7.4.2) from the main
69 branch.
88 7. If all is right, commit the changes to the release branch:
94 8. Tag the repository release branch with the version, e.g.:
101 `configure.ac` and `NEWS` in the *main* branch (PHP-7.4 for example) to
105 changes to the main branch.
110 (a local temporary branch should be used).
114 git push origin {main branch}
115 git push origin {release branch}
192 1. Checkout your release branch, you should have created when releasing
199 branch. Don't forget to update `NEWS` manually in an extra commit then.
366 ## Forking a new release branch
369 branch is about to be cut. Try to be specific about when the branch will
374 2. Just prior to cutting X.Y.0RC1, create the new branch locally.
376 Add a commit on master after the branch point clearing the `NEWS`,
382 Also list the new branch in `CONTRIBUTING.md`.
390 Push the new branch and the commit just added to master.
392 3. Immediately notify internals@ of the branch cut and advise the new merging
398 the new branch. Example:
419 branch:
