Lines Matching refs:g
131 > branch for the pre-GA release, e.g., `PHP-8.2`. See
203 the correct Bison and re2c versions, e.g., for PHP 7.4, Bison 3.0.0 and re2c
243 your release (e.g., `PHP-8.2`) and bump the version numbers in
260 > Version branches (e.g. `PHP-8.1`) will *always* have version numbers in
262 > Patch-level version branches (e.g. `PHP-8.1.7`) will also *always* have
268 > end in `-dev` (e.g., `8.1.7`, `8.1.7RC1`, `8.2.0alpha1`, etc.).
321 `https://downloads.php.net/~yourname/`, e.g. https://downloads.php.net/~derick/.
362 there is a new release, and highlight the major changes (e.g., security
460 (e.g., `PHP-8.1.7`).
468 the base branches and [merged upwards as usual][] (e.g. commit the CVE fix
507 the correct Bison and re2c versions, e.g., for PHP 7.4, Bison 3.0.0 and re2c
669 Find the part of the `$data` array that is related to your version (e.g.,
673 * Set `version` to the full version number (e.g. '8.2.1')
674 * Set `date` to the release date in `j M Y` format (e.g. '5 Jan 2021')
694 7. Update the ChangeLog file for the given major version (e.g., `ChangeLog-8.php`).
698 with the new version and initial anchor (e.g. `<a id="PHP_8_4"></a>` if added
739 * Make sure the tarballs are available from, e.g.,
745 e.g., https://www.php.net/ChangeLog-8.php
747 e.g., `https://www.php.net/releases/X_Y_Z.php`
807 (X.Y=major.minor release, e.g. '8.0'):
809 * `version` to the full version number (e.g. '8.0.1-pl1')
810 * `date` to the release date in `j M Y` format (e.g. '9 Jan 2021')
883 appropriate commit message (e.g., "master is now for PHP 8.3.0-dev").
