RELEASE-PROCEDURE: remove the github upload part

... as we're HTTPS on the main site now, there's no point in that
extra step

diff --git a/docs/RELEASE-PROCEDURE b/docs/RELEASE-PROCEDURE
index 6dafb65a59ea05921da64e7b56ff3942d6aafa6c..b0700f343223e3eb0c4ca3bb26ad7d51d68c86bc 100644 (file)
--- a/docs/RELEASE-PROCEDURE
+++ b/docs/RELEASE-PROCEDURE
@@ -11,8 +11,8 @@ in the source code repo
 - make sure all relevant changes are committed on the master branch
 
 - tag the git repo in this style: `git tag -a curl-7_34_0`. -a annotates the
-  tag and we use underscores instead of dots in the version number. 
-   
+  tag and we use underscores instead of dots in the version number.
+
 - run "./maketgz 7.34.0" to build the release tarballs. It is important that
   you run this on a machine with the correct set of autotools etc installed
   as this is what then will be shipped and used by most users on *nix like
@@ -24,8 +24,6 @@ in the source code repo
 
 - upload the 8 resulting files to the primary download directory
 
-- upload the 4 tarballs to github for the HTTPS download
-
 in the curl-www repo
 --------------------