Skip to content

Commit 1c56000

Browse files
committed
Simplify phpize
1 parent 68e351c commit 1c56000

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/release-process.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ credits files in ext/standard.
6565

6666
4. Checkout the release branch for this release (e.g., PHP-5.4.2) from the main branch.
6767

68-
5. Bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac``, ``scripts/phpize.m4`` and possibly ``NEWS``.
68+
5. Bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac`` and possibly ``NEWS``.
6969
Do not use abbreviations for alpha and beta. Do not use dashes, you should
7070
``#define PHP_VERSION "5.4.22RC1"`` and not ``#define PHP_VERSION "5.4.22-RC1"``
7171

@@ -79,7 +79,7 @@ Do not use abbreviations for alpha and beta. Do not use dashes, you should
7979
9. Tag the repository release branch with the version, e.g.:
8080
``git tag -u YOURKEYID php-5.4.2RC2``
8181

82-
10. Bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac``, ``scripts/phpize.m4`` and ``NEWS``
82+
10. Bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac`` and ``NEWS``
8383
in the *main* branch (PHP-5.4 for example) to prepare for the **next** version.
8484
F.e. if the RC is "5.4.1RC1" then the new one should be "5.4.2-dev" - regardless if we get
8585
a new RC or not. This is to make sure ``version_compare()`` can correctly work.
@@ -162,7 +162,7 @@ Rolling a stable release
162162
------------------------
163163

164164
1. Checkout your release branch, you should have created when releasing previous RC
165-
and bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac``, ``scripts/phpize.m4`` and possibly ``NEWS``.
165+
and bump the version numbers in ``main/php_version.h``, ``Zend/zend.h``, ``configure.ac`` and possibly ``NEWS``.
166166

167167
2. If a CVE commit needs to be merged to the release, then have it committed to
168168
the base branches and merged upwards as usual (f.e commit the CVE fix to 5.3,
@@ -336,7 +336,7 @@ Forking a new release branch
336336

337337
2. Just prior to cutting X.Y.0beta1, create the new branch locally.
338338
Add a commit on master after the branch point clearing the NEWS, UPGRADING
339-
and UPGRADING.INTERNALS files, updating the version in configure.ac and scripts/phpize.m4 (run
339+
and UPGRADING.INTERNALS files, updating the version in configure.ac (run
340340
./configure to automatically update main/php_versions.h, too) and Zend/zend.h.
341341
Also list the new branch in CONTRIBUTING.md.
342342
Example: http://git.php.net/?p=php-src.git;a=commit;h=a63c99b

scripts/phpize.m4

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
dnl This file becomes configure.ac for self-contained extensions.
22

33
AC_PREREQ([2.68])
4-
AC_INIT([PHP],[7.4.0-dev],[https://bugs.php.net],[php],[https://www.php.net])
4+
AC_INIT
55
AC_CONFIG_SRCDIR([config.m4])
66
AC_CONFIG_AUX_DIR([build])
77
AC_PRESERVE_HELP_ORDER

0 commit comments

Comments
 (0)