Lines Matching refs:version
91 5. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
96 When releasing the first alpha version, bump also API version numbers in
103 re2c version (for PHP 7.4, minimum Bison 3.0.0 and re2c 0.13.4 are used).
105 7. Check `./sapi/cli/php -v` output for version matching.
113 9. Tag the repository release branch with the version, e.g.:
119 10. Bump the version numbers in `main/php_version.h`, `Zend/zend.h`,
121 prepare for the **next** version. For example, if the RC is "7.4.1RC1" then
139 13. Run `scripts/dev/gen_verify_stub <version> [identity]`, this will sign the
162 the given version.
209 previous RC and bump the version numbers in `main/php_version.h`,
224 re2c version (for PHP 7.4, minimum Bison 3.0.0 and re2c 0.13.4 are used).
226 6. Check `./sapi/cli/php -v` output for version matching.
228 7. Tag the repository with the version e.g. `git tag -u YOURKEYID php-7.4.1`
241 10. Run `scripts/dev/gen_verify_stub <version> [identity]`, this will sign the
273 version, and the second number is the minor version (7.4 in this example).
278 2. Update `phpweb/include/version.inc` (X_Y=major_minor release number):
280 * `$PHP_X_Y_VERSION` to the correct version
293 4. Update `php-qa/include/release-qa.php` and add the next version as an
296 5. Update the ChangeLog file for the given major version
343 ## Re-releasing the same version (or -pl)
347 2. Update `phpweb/include/version.inc` (X_Y=major_minor release number):
350 * `$PHP_X_Y_VERSION` to the correct version
363 4. Commit all the changes (`include/version.inc`, `archive/archive.xml`,
377 1. One week prior to cutting X.Y.0beta1, warn internals@ that your version's
386 `UPGRADING` and `UPGRADING.INTERNALS` files, updating the version in
389 version also in `win32/build/confutils.js`.
393 Bump API version numbers in `Zend/zend_extensions.h`, `Zend/zend_modules.h`,
411 ## Preparing for the initial stable version (PHP X.Y.0)
415 have done it before you release the initial stable version, since you want
421 ## Prime the selection of the Release Managers of the next version
