@@ -118,11 +118,11 @@ Getting the non stable release (alpha/beta/RC) announced
118118
119119 Note: Remember to update the sha256 checksum information.
120120
121- 2. Update ``web/php.git/include/version.inc`` (x=major version number)
121+ 2. Update ``web/php.git/include/version.inc`` (X_Y=major_minor version number)
122122
123- a. ``$PHP_x_RC `` = "5.4.0RC1" (should be set to "false" before)
123+ a. ``$PHP_X_Y_RC `` = "5.4.0RC1" (should be set to "false" before)
124124
125- b. ``$PHP_x_RC_DATE `` = "06 September 2007"
125+ b. ``$PHP_X_Y_RC_DATE `` = "06 September 2007"
126126
1271273. Skip this step for non stable releases after GA of minor or major versions
128128 (e.g. announce 7.3.0RC1, but not 7.3.1RC1):
@@ -184,7 +184,7 @@ credits files in ext/standard.
184184
1851858. Push the tag f.e. "``git push origin php-5.4.1``"
186186
187- 9. run: ``PHPROOT=. ./makedist php 5.4.1``, this will export the tag, create configure
187+ 9. run: ``PHPROOT=. ./makedist 5.4.1``, this will export the tag, create configure
188188and build three tarballs (gz, bz2 and xz).
189189 Check if the pear files are updated (phar).
190190 On some systems the behavior of GNU tar can default to produce POSIX compliant archives
@@ -224,19 +224,22 @@ Getting the stable release announced
224224 b. If that fails for any non-trivially fixable reason, you can
225225 manually copy the old information to include/releases.inc
226226
227- 2. Edit ``phpweb/include/version.inc`` and change (X=major release number):
227+ 2. Update ``phpweb/include/version.inc`` (X_Y=major_minor release number):
228228
229- a. ``$PHP_X_VERSION `` to the correct version
229+ a. ``$PHP_X_Y_VERSION `` to the correct version
230230
231- b. ``$PHP_X_DATE `` to the release date
231+ b. ``$PHP_X_Y_DATE `` to the release date
232232
233- c. ``$PHP_X_SHA256 `` array and update all the SHA256 sums
233+ c. ``$PHP_X_Y_SHA256 `` array and update all the SHA256 sums
234234
235- d. set ``$PHP_X_RC `` to false!
235+ d. set ``$PHP_X_Y_RC `` to false!
236236
237237 e. Make sure there are no outdated "notes" or edited "date" keys in the
238238 ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array
239239
240+ f. Only for the first revision of a major or minor release bump
241+ ``$PHP_X_VERSION``, ``$PHP_X_DATE`` and ``$PHP_X_RC_DATE``.
242+
2402433. Create the release file (releases/x_y_z.php)
241244 Usually we use the same content as for point 6, but included in php template
242245 instead of the release xml.
@@ -295,15 +298,15 @@ Re-releasing the same version (or -pl)
295298
2962991. Commit the new binaries to ``phpweb/distributions/``
297300
298- 2. Edit ``phpweb/include/version.inc`` and change (X=major release number):
301+ 2. Update ``phpweb/include/version.inc`` (X_Y=major_minor release number):
299302
300303 a. If only releasing for one OS, make sure you edit only those variables
301304
302- b. ``$PHP_X_VERSION `` to the correct version
305+ b. ``$PHP_X_Y_VERSION `` to the correct version
303306
304- c. ``$PHP_X_DATE `` to the release date
307+ c. ``$PHP_X_Y_DATE `` to the release date
305308
306- d. ``$PHP_X_SHA256 `` array and update all the SHA256 sums
309+ d. ``$PHP_X_Y_SHA256 `` array and update all the SHA256 sums
307310
308311 e. Make sure there are no outdated "notes" or edited "date" keys in the
309312 ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array
0 commit comments