diff options
author | Hannes Magnusson <bjori@php.net> | 2015-04-17 10:05:32 -0700 |
---|---|---|
committer | Hannes Magnusson <bjori@php.net> | 2015-04-17 10:05:32 -0700 |
commit | 983f155e1ca47ac6eedd68922b86248b03b45096 (patch) | |
tree | 63911f1ff457305ed292f1c96b8b9efeab6f0620 | |
parent | 0d562a8f44d0ac425cc5d3b95cd1f62f3d295664 (diff) | |
download | php-git-983f155e1ca47ac6eedd68922b86248b03b45096.tar.gz |
phpweb now publishes SHA256s -- and please don't cc php-announce@ - make it seperate mail
-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 de166e418f..507ab9967d 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -200,12 +200,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 @@ -254,6 +256,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) -------------------------------------- @@ -270,7 +275,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 @@ -287,3 +294,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. |