diff options
| author | Hannes Magnusson <bjori@php.net> | 2015-04-17 10:06:31 -0700 |
|---|---|---|
| committer | Hannes Magnusson <bjori@php.net> | 2015-04-17 10:06:31 -0700 |
| commit | b5b8cd50741bd5726e9a1bfc4025e48b63eb6d96 (patch) | |
| tree | 3307629adea4574c91e94bb0e67c7f875aef867e | |
| parent | e09febb286b08a0a7bdbd8a63435eac8963906c4 (diff) | |
| parent | 983f155e1ca47ac6eedd68922b86248b03b45096 (diff) | |
| download | php-git-b5b8cd50741bd5726e9a1bfc4025e48b63eb6d96.tar.gz | |
Merge branch 'PHP-5.4' into PHP-5.5
* PHP-5.4:
phpweb now publishes SHA256s -- and please don't cc php-announce@ - make it seperate mail
Fixed res leak
| -rw-r--r-- | README.RELEASE_PROCESS | 18 |
1 files changed, 14 insertions, 4 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index f0a8aca688..84e22a35a9 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -213,12 +213,14 @@ Getting the stable release announced c. ``$PHP_X_MD5`` array and update all the md5 sums - d. set ``$PHP_X_RC`` to false! + d. ``$PHP_X_SHA256`` array and update all the SHA256 sums - e. Make sure there are no outdated "notes" or edited "date" keys in the + e. set ``$PHP_X_RC`` to false! + + f. Make sure there are no outdated "notes" or edited "date" keys in the ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array - f. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows") + g. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows") 3. Create the release file (releases/x_y_z.php) Usually we use the same content as for point 6, but included in php template @@ -267,6 +269,9 @@ to upgrade. 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. +Please make sure that the mail to php-announce@ is its own completely seperate email. +This is to make sure that repiles to the announcement on php-general@ or internals@ +will not accidentally hit the php-announce@ mailinglist. Re-releasing the same version (or -pl) -------------------------------------- @@ -283,7 +288,9 @@ Re-releasing the same version (or -pl) d. ``$PHP_X_MD5`` array and update all the md5 sums - e. Make sure there are no outdated "notes" or edited "date" keys in the + e. ``$PHP_X_SHA256`` array and update all the SHA256 sums + + f. Make sure there are no outdated "notes" or edited "date" keys in the ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array 3. Add a short notice to phpweb stating that there is a new release, and @@ -300,3 +307,6 @@ to upgrade. 5. 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 the news entry. +Please make sure that the mail to php-announce@ is its own completely seperate email. +This is to make sure that repiles to the announcement on php-general@ or internals@ +will not accidentally hit the php-announce@ mailinglist. |