Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 164 lines (85 sloc) 7.175 kb
193b11c - port from todo wiki to reST (http://wiki.pooteeweet.org/ReleaseCheckli...
Lukas Smith authored
1 =======================
2 PHP Release Process
3 =======================
4
5 Rolling a release candidate
6 ---------------------------
7
8 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.)
9
10 2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
11
12 3. Commit those changes
13
14 4. tag the repository with "``cvs tag php_4_4_1RC1``" (of course, you need to change that to the version you're rolling an RC for). When making 5.X release, you need to tag the Zend directory separately!!
15
16 5. Bumb up the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS`` again, to the **next** version. F.e. if the release candidate was "4.4.1RC1" then the new one should be "4.4.1RC2-dev" - regardless if we get a new RC or not. This is to make sure ``version_compare()`` can correctly work.
17
18 6. Commit those changes
19
20 7. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4 branch if you're rolling 4.4.x releases).
21
22 8. You do not have to update the tree, but ofcourse you can with "``cvs up -dP``".
23
24 9. run: ``./makedist php 4.4.1RC1``, this will export the tree, create configure and build two tarballs (one gz and one bz2).
25
26 10. Copy those two tarballs to www.php.net, in your homedir their should be a directory "downloads/". Copy them into there, so that the system can generate MD5 sums. If you do not have this directory, talk to Derick.
27
28 11. Now the RC can be found on http://downloads.php.net/yourname, f.e. http://downloads.php.net/derick/
29
30 12. Once the release has been tagged, contact Edin Kadribasic (edink @ usual php e-mail) so that Windows binaries can be created. Once those are made, they should be placed into the same directory as the source snapshots.
31
32 Getting the Release Candidate out there
33 ---------------------------------------
34
35 1. Send an email (see example here: http://news.php.net/php.internals/19486) **To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` lists pointing out "the location of the release" and "the possible release date of either the next RC, or the final release".
36
37 2. Send an email (see example here http://news.php.net/php.qa/26069) **To** ``php-qa@lists.php.net`` and **Bcc** everybody on the PhP4yz, PhP5yz or PhP6yz list (depending on the PHP version). This email is to notify the selected projects about a new RC so that they can make sure their projects keep working.
38
39 3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``.
40
41 4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and commit this.
42
43 a. ``$BUILD_TEST_RELEASES`` = array("4.4.7RC1", "5.2.2RC1")
44
45 b. ``$CURRENT_QA_RELEASE_4`` = "4.4.7RC1" (``$CURRENT_QA_RELEASE_5`` for PHP5)
46
47 c. ``$RELEASE_PROCESS`` = array(4 => true, 5 => true)
48
49 1. Update in ``php-bugs-web/include/functions.inc`` the ``show_version_option`` function to include the new RC and commit.
50
51 2. Run the bumpRelease script for phpweb
52
53 a. ``php bin/bumpRelease 5`` (or ``php bin/bumpRelease 4`` for PHP4)
54
55 3. Update ``phpweb/include/version.inc`` (x=major version number)
56
57 a. ``$PHP_x_RC`` = "5.3.0RC1"
58
59 b. ``$PHP_x_RC_DATE`` = "06 September 2007"
60
61 4. Commit those changes:
62
63 a. ``cvs commit include/version.inc include/releases.inc``
64
65 Rolling a release
66 -----------------
67
68 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.)
69
70 2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``.
71
72 3. **Merge** all related sections in NEWS (f.e. merge the 4.4.1RC1 and 4.4.0 sections)
73
74 4. Commit those changes
75
76 5. tag the repository with "``cvs tag php_4_4_1``" (of course, you need to change that to the version you're rolling an RC for). When making 5.X release, you need to tag the Zend directory separately!!
77
78 6. Bumb up the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS`` again, to the **next** version. F.e. if the release candidate was "4.4.1RC1" then the new one should be "4.4.1RC2-dev" - regardless if we get a new RC or not. This is to make sure ``version_compare()`` can correctly work.
79
80 7. Commit those changes
81
82 8. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4 branch if you're rolling 4.4.x releases).
83
84 9. You do not have to update the tree, but ofcourse you can with "``cvs up -dP``".
85
86 10. run: ``./makedist php 4.4.1``, this will export the tree, create configure and build two tarballs (one gz and one bz2).
87
88 11. Commit those two tarballs to CVS (phpweb/distributions)
89
90 12. Once the release has been tagged, contact Edin Kadribasic (edink @ usual php e-mail) so that Windows binaries can be created. Once those are made, they should be committed to CVS too.
91
92 13. Check if the pear files are updated (phar for 5.1+ or run pear/make-pear-bundle.php with 4.4)
93
94 14. When making a final release, also remind Edin to ask John to prepare the installer packages for Win32.
95
96 Getting the Release out there
97 -----------------------------
98
99 1. Run the bumpRelease script for phpweb
100
101 a. ``php bin/bumpRelease 5`` (or ``php bin/bumpRelease 4`` for PHP4)
102
103 2. Edit ``phpweb/include/version.inc`` and change (X=major release number):
104
105 a. ``$PHP_X_VERSION`` to the correct version
106
107 b. ``$PHP_X_DATE`` to the release date
108
109 c. ``$PHP_X_MD5`` array and update all the md5 sums
110
111 d. set ``$PHP_X_RC`` to false!
112
113 e. Make sure there are no outdated "notes" or edited "date" keys in the ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array
114
115 f. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows")
116
117 3. Update the ChangeLog file ``ChangeLog-4.php`` from the NEWS file
118
119 a. go over the list and put every element on one line
120
121 b. check for &, < and > and escape them if necessary
122
123 c. remove all the names at the ends of lines
124
125 d. for marking up, you can do the following (with VI):
126
127 I. ``s/^- /<li>/``
128
129 II. ``s/$/<\/li>/``
130
131 III. ``s/Fixed bug #\([0-9]\+\)/<?php bugfix(\1); ?>/``
132
133 4. ``cp releases/4_4_0.php releases/4_4_1.php``
134
135 5. ``cvs add releases/4_4_1.php``
136
137 6. Update the releases/*.php file with relevant data. The release announcement file should list in detail:
138
139 a. security fixes,
140
141 b. changes in behaviour (whether due to a bug fix or not)
142
143 7. Add a short notice to phpweb stating that there is a new release, and highlight the major important things (security fixes) and when it is important to upgrade.
144
145 a. php bin/createNewsEntry
146
147 8. Commit all the changes, do not release on Fridays, Saturdays or Sundays because the sysadmins can not upgrade stuff then.
148
149 9. Wait an hour or two, then send a mail to php-announce@lists.php.net, php-general@lists.php.net and internals@lists.php.net with a text similar to http://news.php.net/php.internals/17222.
150
151 10. Update ``php-bugs-web/include/functions.php`` to include the new version number, and remove the RC from there.
152
153 11. Update ``qaweb/include/release-qa.php``
154
155 a. Update the $BUILD_TEST_RELEASES array with the release name
156
157 b. Update $RELEASE_PROCESS array (set to false)
158
159 I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false
160
161 II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false
162
163 12. Rebuild the English and Japanese docs (ask Derick)
Something went wrong with that request. Please try again.