Lines Matching refs:branch

67    > Check the CI status for your branch periodically and resolve the failures
120 3. Check out the *release branch* for this release from the *version branch*.
123    > There is no *version branch* for alpha or beta releases. Instead, treat the
124    > main branch as the version branch. You will create a local-only release
125    > branch from the main branch. Do not push it!
128    > git checkout -b php-X.Y.0alpha1-local-release-branch upstream/master
132    > branch for the pre-GA release, e.g., `PHP-8.2`. See
133    > "[Forking a new version branch](#forking-a-new-version-branch)" below.
135    > this version branch. Again, these release branches are local-only. Do not
139    > git checkout -b php-X.Y.0beta2-local-release-branch upstream/PHP-X.Y
143    > After GA, you will create (and push) a new *patch-level version branch*
146    > version branch from the `PHP-8.2` version branch.
153    > We will use the patch-level version branch to commit any critical bug or
156    > Then, from the patch-level version branch, you will create another
157    > local-only release branch. Do not push this one!
160    > git checkout -b php-X.Y.ZRC1-local-release-branch upstream/PHP-X.Y.Z
163 4. Using your local-only release branch, bump the version numbers in
230 7. If all is correct, commit the changes to your local-only release branch.
237 8. Tag your local-only release branch with the release version.
243 9. �� **For post-GA releases only,** switch back to the *version branch* for
246    the version branch for the next version.
249    branch should be bumped to `8.2.2-dev`. We do this regardless of whether we
253    Commit the changes to the version branch.
264    > version numbers that end in `-dev` in these files. The main branch (i.e.
275     git push upstream PHP-X.Y.Z    # patch-level version branch (post-GA only)
276     git push upstream PHP-X.Y      # version branch
461 1. Check out the *patch-level version branch* for the release
465    > You should have created this branch when packaging the non-stable release
471    patch-level version branch for this release.
473    Commit these changes and push the patch-level version branch. Ensure
478    > patch-level version branch.
480 3. Run the `./scripts/dev/credits` script in the patch-level version branch,
486    > cherry-picked into this branch.
488 4. Create a local-only release branch for this release from the *patch-level
489    version branch*.
492    git checkout -b php-X.Y.Z-local-release-branch upstream/PHP-X.Y.Z
495 5. Using your local-only release branch, bump the version numbers in
500    the version numbers in the patch-level version branch should be
501    `8.1.8-dev`. In your local-only release branch, you will change them all to
534 8. If all is correct, commit the changes to your local-only release branch.
541 9. Tag your local-only release branch with the release version and push the tag.
845 ## Forking a new version branch
848 version branch. This frees up the main branch (i.e., `master`) for any new
852    branch is about to be created. Be specific about when the branch creation
855 2. Just prior to tagging `X.Y.0RC1`, create the new version branch locally,
858 3. Add a commit on the main branch (i.e., `master`) after the branch point.
867    * add the new branch to the list in `CONTRIBUTING.md`.
872 4. Push the new version branch and the changes to the `master` branch, with an
875 5. Immediately notify internals@ of the new branch and advise on the new merging
879    the new branch.
887 > We create the new version branch at the first release candidate rather than at
889 > version ready for RC and GA. During this time, the main branch is *only* for
913 release managers for the latest version branch should issue a call for
949    your username alongside your branch.