Lines Matching refs:to
11 2. Package two days before a release. So if the release is to be on Thursday,
16 It is recommended to do so a couple of days before the packaging day, to
17 have enough time to investigate failures, communicate with the authors and
26 5. Follow all steps to the letter. When unclear ask previous RM's (David/Julien/
28 first releases one of the previous RM's is around to answer questions. For the
29 steps related to the php/QA/bug websites try to have someone from the webmaster
32 6. Verify the tags to be extra sure everything was tagged properly.
34 7. Moving extensions from/to PECL requires write acces to the destination.
37 Moving extensions from php-src to PECL
41 no trunk at this point and commit this to svn
43 - Move the extension from php-src to the new location
53 For Moving extensions from PECL to php-src the svn mv has to be tone the other
77 8. If all is right, commit the changes to the release branch with ``git commit -a``.
83 in the *main* branch (PHP-5.4 for example) to prepare for the **next** version.
85 a new RC or not. This is to make sure ``version_compare()`` can correctly work.
86 Commit the changes to the main branch.
88 11. Push the changes to the main repo, the tag, the main branch and the release branch :
96 13. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there should be a
98 MD5 sums. If you do not have this directory, talk to Derick or Dan.
117 This email is to notify the selected projects about a new release so that they
128 and RCs are configured here. Only $QA_RELEASES needs to be edited.
133 Note: Remember to update the MD5 checksum information.
137 a. ``$PHP_x_RC`` = "5.4.0RC1" (should be set to "false" before)
154 2. If a CVE commit needs to be merged to the release, then have it committed to
155 the base branches and merged upwards as usual (f.e commit the CVE fix to 5.3,
156 merge to 5.4, 5.5 etc...). Then you can cherry-pick it in your release branch.
157 Don't forget to update NEWS manually in an extra commit then.
181 11. Commit and push all the tarballs and signature files to web/php-distributions.git,
190 This is to fetch the last commit id from php-distributions.git and commit this
191 last commit id to web/php.git, then, mirrors will now sync
203 highest branch, otherwise you have to do this manually, see point 1.b
206 to manually copy the old information to include/releases.inc
210 a. ``$PHP_X_VERSION`` to the correct version
212 b. ``$PHP_X_DATE`` to the release date
218 e. set ``$PHP_X_RC`` to false!
253 e. You may want to try php-web/bin/news2html to automate this task
255 6. Add a short notice to phpweb stating that there is a new release, and
257 to upgrade.
267 8. Commit all the changes to their respective git repos
269 9. Wait an hour or two, then send a mail to php-announce@lists.php.net,
270 php-general@lists.php.net and internals@lists.php.net with a text similar to
272 Please make sure that the mail to php-announce@ is its own completely seperate email.
273 This is to make sure that repiles to the announcement on php-general@ or internals@
279 1. Commit the new binaries to ``phpweb/distributions/``
285 b. ``$PHP_X_VERSION`` to the correct version
287 c. ``$PHP_X_DATE`` to the release date
296 3. Add a short notice to phpweb stating that there is a new release, and
298 to upgrade.
307 5. Wait an hour or two, then send a mail to php-announce@lists.php.net,
308 php-general@lists.php.net and internals@lists.php.net with a text similar to
310 Please make sure that the mail to php-announce@ is its own completely seperate email.
311 This is to make sure that repiles to the announcement on php-general@ or internals@
