MD5 checksums are history

According to a respective RFC[1], the MD5 checksums have been removed
from the release notes and the API.  Also, no checksums are generated
after uploading the tarballs to the user directories
on downloads.php.net.

[1] <https://wiki.php.net/rfc/release-md5-deprecation>

1 files changed, 8 insertions, 13 deletions

diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index 93b23e1cb7..c391de8972 100644
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -97,8 +97,7 @@ and build three tarballs (gz, bz2 and xz).
 and output verification information to be included in announcement email
 
 14. Copy those tarballs (scp, rsync) to downloads.php.net, in your homedir there should be a
-directory "public_html/". Copy them into there, so that the system can generate
-MD5 sums. If you do not have this directory, create it.
+directory "public_html/". Copy them into there. If you do not have this directory, create it.
 
 15. Now the RC can be found on http://downloads.php.net/~yourname,
 f.e. http://downloads.php.net/~derick/
@@ -117,7 +116,7 @@ Getting the non stable release (alpha/beta/RC) announced
    Example: When rolling an RC, set the 'rc' with appropriate information for the
    given version.
 
-   Note: Remember to update the MD5 and sha256 checksum information.
+   Note: Remember to update the sha256 checksum information.
 
 2. Update ``web/php.git/include/version.inc`` (x=major version number)
 
@@ -228,16 +227,14 @@ Getting the stable release announced
 
  b. ``$PHP_X_DATE`` to the release date
 
- c. ``$PHP_X_MD5`` array and update all the md5 sums
+ c. ``$PHP_X_SHA256`` array and update all the SHA256 sums
 
- d. ``$PHP_X_SHA256`` array and update all the SHA256 sums
-
- e. set ``$PHP_X_RC`` to false!
+ d. set ``$PHP_X_RC`` to false!
 
- f. Make sure there are no outdated "notes" or edited "date" keys in the
+ e. Make sure there are no outdated "notes" or edited "date" keys in the
  ``$RELEASES[X][$PHP_X_VERSION]["source"]`` array
 
- g. if the windows builds aren't ready yet prefix the "windows" key with a dot (".windows")
+ f. 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
@@ -305,11 +302,9 @@ Re-releasing the same version (or -pl)
 
  c. ``$PHP_X_DATE`` to the release date
 
- d. ``$PHP_X_MD5`` array and update all the md5 sums
-
- e. ``$PHP_X_SHA256`` array and update all the SHA256 sums
+ d. ``$PHP_X_SHA256`` array and update all the SHA256 sums
 
- f. Make sure there are no outdated "notes" or edited "date" keys in the
+ e. 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