Lines Matching refs:release

1 # PHP release process
3 A release managers role includes making packaged source code from the canonical repository
4 available according to their release schedule.
6 The release schedule for their branch is available on a Wiki page, for example
7   [PHP 8.0 release schedule](https://wiki.php.net/todo/php80)
9 There are two types of release:
17 Before a release manager can begin their work, there are several things that must happen,
19 	[New Release Manager Checklist](#new-release-manager-checklist).
23  1. Do not release on Fridays, Saturdays, or Sundays as this gives poor lead time for 
26  2. Package two days before a release. So if the release is to be on Thursday,
52  6. There is a PHP release Docker image https://github.com/sgolemon/php-release
55  7. Communication with previous release managers should be conducted via
56     release-managers@php.net
61 ## Packaging a non stable release (alpha/beta/RC)
68  3. Checkout the release branch for this release (e.g., PHP-7.4.2) from the main
76     ⚠️  When releasing the **first release candidate**, you must also bump the API
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.:
109     Non stable release branches don't need to be pushed 
115     git push origin {release branch}
132 15. Once the release has been tagged, contact the release-managers@ distribution
136 ## Announcing a non stable release (alpha/beta/RC)
138  1. Update `web-qa:include/release-qa.php` with the appropriate information. See
139     the documentation within release-qa.php for more information, but all
151     Add a short notice to web-php stating that there is a new release, and
171     `php-general@lists.php.net` lists pointing out "the location of the release"
172     and "the possible release date of either the next RC, or the final release".
178     emails are to notify the selected projects about a new release so that they
187  6. For RCs, post tweet with release announcement (and link to news article on
190 ## Packaging a stable release
192  1. Checkout your release branch, you should have created when releasing
196  2. If a CVE commit needs to be merged to the release, then have it committed to
198     7.2, merge to 7.3, 7.4 etc...). Then you can cherry-pick it in your release
247 12. Once the release has been tagged, contact release managers, Windows
251 ## Announcing a stable release
253  1. Update `web-php:include/releases.inc` with the old release info (updates the
263     (X.Y=major.minor release, e.g. '8.0'):
266     * `date` to the release date in `j M Y` format (e.g. '5 Jan 2021')
267     * `tags` array should include `security` if this is a security release
270  3. Create the release file (`releases/x_y_z.php`):
274     Add `--security` for a security release.
277     template instead of the release xml.
281  4. Update `web-qa:include/release-qa.php` and add the next version as an
283     no more QA releases. Setting the release number to 0 is sufficient to
284     remove the old QA release from the available QA releases list.
307  6. Add a short notice to `web-php` stating that there is a new release, and
323     included in the release mail.
332 11. Post tweet with release announcement and link to news article on php.net
340     (X.Y=major.minor release, e.g. '8.0'):
343     * `date` to the release date in `j M Y` format (e.g. '9 Jan 2021')
344     * `tags` array should include `security` if this is a security release
347  3. Add a short notice to `web-php` stating that there is a new release, and
366 ## Forking a new release branch
404  1. About the time you release the first RC, remind the documentation team
406     have done it before you release the initial stable version, since you want
407     to link to it in the release announcements.
410     release.
414     sections for each pre-release.
418 This should be done by one of the release managers of the latest release
421  1. About three months before the scheduled release of the first alpha of the
422     next minor or major release, issue a call for volunteers on
429  3. Help the new release managers with their first steps.
434     to the release-managers@ distribution list.
447     primary-qa-tester@lists.php.net lists, to be able to moderate your release