You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.RELEASE_PROCESS
+12-20
Original file line number
Diff line number
Diff line change
@@ -50,38 +50,30 @@ Rolling a non stable release (alpha/beta/RC)
50
50
2. run the "scripts/dev/credits" script in php-src and commit the changes in the
51
51
credits files in ext/standard.
52
52
53
-
3. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
54
-
Do not use abbreviations for alpha and beta.
55
-
56
-
4. Commit those changes and note the revision id.
57
-
58
-
5. tag the repository with the version. To do the tag in a fast way do a svn copy on the server using full URLs. You should use the revision id from the above commit to prevent mistakes in case there was a commit in between. f.e. "``svn cp https://svn.php.net/repository/php/php-src/branches/PHP_5_3@308399 https://svn.php.net/repository/php/php-src/tags/php_5_3_6RC1``"
59
-
(of course, you need to change that to the version you're rolling an RC for). Mail php-internals to announce the tag so tests/validation/check can be done prior to package it. It is especially important for RCs.
53
+
3. Checkout the release branch for this release (e.g., PHP-5.4.2).
60
54
61
-
6. Bump up the version numbers in ``main/php_version.h``, ``configure.in``
62
-
and possibly ``NEWS`` again, to the **next** version. F.e. if the release
63
-
candidate was "4.4.1RC1" then the new one should be "4.4.1RC2-dev" - regardless
64
-
if we get a new RC or not. This is to make sure ``version_compare()`` can
65
-
correctly work.
55
+
4. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
56
+
Do not use abbreviations for alpha and beta.
66
57
67
-
7. Commit those changes
58
+
5. Commit these changes to the branch with ``git commit -a``.
68
59
69
-
8. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4
70
-
branch if you're rolling 4.4.x releases).
60
+
6. Tag the repository with the version, e.g.:
61
+
``git tag -u YOURKEYID PHP-5.4.2-RC2``
71
62
72
-
9. You do not have to update the tree, but of course you can with "``svn up``".
63
+
7. Push the changes to the main repo:
64
+
``git push --tags origin HEAD``
73
65
74
-
10. run: ``./makedist php 4.4.1RC1``, this will export the tree, create configure
66
+
8. run: ``./makedist 5.4.2-RC2``, this will export the tree, create configure
75
67
and build two tarballs (one gz and one bz2).
76
68
77
-
11. Copy those two tarballs to www.php.net, in your homedir there should be a
69
+
9. Copy those two tarballs to www.php.net, in your homedir there should be a
78
70
directory "downloads/". Copy them into there, so that the system can generate
79
71
MD5 sums. If you do not have this directory, talk to Derick.
80
72
81
-
12. Now the RC can be found on http://downloads.php.net/yourname,
73
+
10. Now the RC can be found on http://downloads.php.net/yourname,
0 commit comments