Lines Matching refs:a
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
38 - Checkout the pecl directory, most likely you want a sparse-root checkout
56 Rolling a non stable release (alpha/beta/RC)
77 8. If all is right, commit the changes to the release branch with ``git commit -a``.
85 a new RC or not. This is to make sure ``version_compare()`` can correctly work.
99 14. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there should be a
120 This email is to notify the selected projects about a new release so that they
122 as a moderator for ``primary-qa-tester@lists.php.net`` by having someone (Hannes, Dan,
140 a. ``$PHP_x_RC`` = "5.4.0RC1" (should be set to "false" before)
146 a. ``git commit -a && git push origin master``
151 Rolling a stable release
157 2. If a CVE commit needs to be merged to the release, then have it committed to
205 a. You can run ``php bin/bumpRelease 5`` if you are making a release for the
213 a. ``$PHP_X_VERSION`` to the correct version
226 g. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows")
238 a. go over the list and put every element on one line
258 6. Add a short notice to phpweb stating that there is a new release, and
262 a. Call php bin/createNewsEntry in your local phpweb checkout
267 Try, f.e. http://www.php.net/get/php-5.5.1.tar.bz2/from/a/mirror
274 10. Wait an hour or two, then send a mail to php-announce@lists.php.net,
275 php-general@lists.php.net and internals@lists.php.net with a text similar to
288 a. If only releasing for one OS, make sure you edit only those variables
301 3. Add a short notice to phpweb stating that there is a new release, and
305 a. Call php bin/createNewsEntry in your local phpweb checkout
312 5. Wait an hour or two, then send a mail to php-announce@lists.php.net,
313 php-general@lists.php.net and internals@lists.php.net with a text similar to
