Lines Matching refs:branch
65 > Check the CI status for your branch periodically and resolve the failures
118 3. Check out the *release branch* for this release from the *version branch*.
121 > There is no *version branch* for alpha or beta releases. Instead, treat the
122 > main branch as the version branch. You will create a local-only release
123 > branch from the main branch. Do not push it!
126 > git checkout -b php-X.Y.0alpha1-local-release-branch upstream/master
130 > branch for the pre-GA release, e.g., `PHP-8.2`. See
131 > "[Forking a new version branch](#forking-a-new-version-branch)" below.
133 > this version branch. Again, these release branches are local-only. Do not
137 > git checkout -b php-X.Y.0beta2-local-release-branch upstream/PHP-X.Y
141 > After GA, you will create (and push) a new *patch-level version branch*
144 > version branch from the `PHP-8.2` version branch.
151 > We will use the patch-level version branch to commit any critical bug or
154 > Then, from the patch-level version branch, you will create another
155 > local-only release branch. Do not push this one!
158 > git checkout -b php-X.Y.ZRC1-local-release-branch upstream/PHP-X.Y.Z
161 4. Using your local-only release branch, bump the version numbers in
228 7. If all is correct, commit the changes to your local-only release branch.
235 8. Tag your local-only release branch with the release version.
245 Commit the changes to the `master` (or `PHP-X.Y`) branch.
252 �� **For post-GA releases only,** switch back to the *version branch* for
255 the version branch for the next version.
258 branch should be bumped to `8.2.2-dev`. We do this regardless of whether we
262 Commit the changes to the version branch.
273 > version numbers that end in `-dev` in these files. The main branch (i.e.
284 git push upstream PHP-X.Y.Z # patch-level version branch (post-GA only)
285 git push upstream PHP-X.Y # version branch
469 1. Check out the *patch-level version branch* for the release
473 > You should have created this branch when packaging the non-stable release
475 > create and push this branch.
480 patch-level version branch for this release.
482 Commit these changes and push the patch-level version branch. Ensure
487 > patch-level version branch.
489 3. Run the `./scripts/dev/credits` script in the patch-level version branch,
495 > cherry-picked into this branch.
497 4. Create a local-only release branch for this release from the *patch-level
498 version branch*.
501 git checkout -b php-X.Y.Z-local-release-branch upstream/PHP-X.Y.Z
504 5. Using your local-only release branch, bump the version numbers in
509 the version numbers in the patch-level version branch should be
510 `8.1.8-dev`. In your local-only release branch, you will change them all to
543 8. If all is correct, commit the changes to your local-only release branch.
550 9. Tag your local-only release branch with the release version and push the tag.
865 ## Forking a new version branch
868 version branch. This frees up the main branch (i.e., `master`) for any new
872 branch is about to be created. Be specific about when the branch creation
875 2. Just prior to tagging `X.Y.0RC1`, create the new version branch locally,
878 3. Add a commit on the main branch (i.e., `master`) after the branch point.
887 * add the new branch to the list in `CONTRIBUTING.md`.
892 4. Push the new version branch and the changes to the `master` branch, with an
895 5. Immediately notify internals@ of the new branch and advise on the new merging
899 the new branch.
907 > We create the new version branch at the first release candidate rather than at
909 > version ready for RC and GA. During this time, the main branch is *only* for
963 release managers for the latest version branch should issue a call for
1029 your username alongside your branch.
