release-process.md - OpenGrok cross reference for /PHP-8.0/docs/release-process.md

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
49         git filter-branch --prune-empty --subdirectory-filter ext/ext-name master
58     * Create branch and tags structure appropriate for the extension and push:
88  4. Checkout the release branch for this release (e.g., PHP-7.4.2) from the main
89     branch.
108  8. If all is right, commit the changes to the release branch:
114  9. Tag the repository release branch with the version, e.g.:
121     `configure.ac` and `NEWS` in the *main* branch (PHP-7.4 for example) to
125     changes to the main branch.
127 11. Push the changes to the main repo, the tag, the main branch and the release
128     branch. Release branches for alpha/beta/.0RCx releases before the GA release
129     don't need to be pushed (a local temporary branch should be used).
133     git push origin {main branch}
134     git push origin {release branch}
211  1. Checkout your release branch, you should have created when releasing
218     branch. Don't forget to update `NEWS` manually in an extra commit then.
388 ## Forking a new release branch
391     branch is about to be cut, and that PHP-X.Y will be moving into feature
392     freeze. Try to be specific about when the branch will be cut.
396  2. Just prior to cutting X.Y.0beta1, create the new branch locally.
398     Add a commit on master after the branch point clearing the `NEWS`,
404     Also list the new branch in `CONTRIBUTING.md`.
410     Push the new branch and the commit just added to master.
412  3. Immediately notify internals@ of the branch cut and advise the new merging
418     the new branch. Example:
441 branch:
468     `main/php_version.h` in a release branch, you need release manager karma in