com php-src: phpweb now publishes SHA256s -- and please don't cc php-announce@ - make it seperate mail: README.RELEASE_PROCE SS
| From: | Hannes Magnusson | Date: | Fri, 17 Apr 2015 17:05:32 +0000 |
| Subject: | com php-src: phpweb now publishes SHA256s -- and please don't cc php-announce@ - make it seperate mail: README.RELEASE_PROCE SS | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-86356@lists.php.net to get a copy of this message | ||
Commit: 983f155e1ca47ac6eedd68922b86248b03b45096
Author: Hannes Magnusson <bjori@php.net> Fri, 17 Apr 2015 10:05:32 -0700
Parents: 0d562a8f44d0ac425cc5d3b95cd1f62f3d295664
Branches: PHP-5.4
Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=983f155e1ca47ac6eedd68922b86248b03b45096
Log:
phpweb now publishes SHA256s -- and please don't cc php-announce@ - make it seperate mail
Changed paths:
M README.RELEASE_PROCESS
Diff:
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index de166e4..507ab99 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.