release-process.md - OpenGrok cross reference for /PHP-7.4/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.
107  8. If all is right, commit the changes to the release branch:
113  9. Tag the repository release branch with the version, e.g.:
120     `configure.ac` and `NEWS` in the *main* branch (PHP-7.4 for example) to
124     changes to the main branch.
126 11. Push the changes to the main repo, the tag, the main branch and the release
127     branch. Release branches for alpha/beta/.0RCx releases before the GA release
128     don't need to be pushed (a local temporary branch should be used).
132     git push origin {main branch}
133     git push origin {release branch}
208  1. Checkout your release branch, you should have created when releasing
215     branch. Don't forget to update `NEWS` manually in an extra commit then.
375 ## Forking a new release branch
378     branch is about to be cut, and that PHP-X.Y will be moving into feature
379     freeze. Try to be specific about when the branch will be cut.
383  2. Just prior to cutting X.Y.0beta1, create the new branch locally.
385     Add a commit on master after the branch point clearing the `NEWS`,
391     Also list the new branch in `CONTRIBUTING.md`.
397     Push the new branch and the commit just added to master.
399  3. Immediately notify internals@ of the branch cut and advise the new merging
405     the new branch. Example:
446     `main/php_version.h` in a release branch, you need release manager karma in