Lines Matching refs:version
68 5. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
72 6. Compile and make test, with and without ZTS, using the right Bison version
75 7. Check ./sapi/cli/php -v output for version matching.
79 9. Tag the repository release branch with the version, e.g.:
82 10. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and ``NEWS``
83 in the *main* branch (PHP-5.4 for example) to prepare for the **next** version.
131 given version.
135 4. Update ``web/php.git/include/version.inc`` (x=major version number)
152 and bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
165 5. Compile and make test, with and without ZTS, using the right Bison version
168 6. Check ./sapi/cli/php -v output for version matching.
170 7. tag the repository with the version f.e. "``git tag -u YOURKEYID -s php-5.4.1``"
208 2. Edit ``phpweb/include/version.inc`` and change (X=major release number):
210 a. ``$PHP_X_VERSION`` to the correct version
229 4. Update php-qa/include/release-qa.php and add the next version as an QARELEASE
232 5. Update the ChangeLog file for the given major version
276 Re-releasing the same version (or -pl)
281 2. Edit ``phpweb/include/version.inc`` and change (X=major release number):
285 b. ``$PHP_X_VERSION`` to the correct version
304 4. Commit all the changes (``include/version.inc``, ``archive/archive.xml``,