build: instructions on how to make a point release

RELEASE.md

@@ -23,7 +23,6 @@ Making a release
   * make upload_website
   * make upload_github
   * make startdev
-  * run bin/tidy-beta <previous version> to tidy old betas
   * # announce with forum post, twitter post, G+ post
 
 Early in the next release cycle update the vendored dependencies
@@ -32,3 +31,25 @@ Early in the next release cycle update the vendored dependencies
   * git status
   * git add new files
   * git commit -a -v
+
+Making a point release.  If rclone needs a point release due to some
+horrendous bug, then
+  * git branch v1.XX v1.XX-fixes
+  * git cherry-pick any fixes
+  * Test (see above)
+  * make NEW_TAG=v1.XX.1 tag
+  * edit docs/content/changelog.md
+  * make TAG=v1.43.1 doc
+  * git commit -a -v -m "Version v1.XX.1"
+  * git tag -d -v1.XX.1
+  * git tag -s -m "Version v1.XX.1" v1.XX.1
+  * git push --tags -u origin v1.XX-fixes
+  * make BRANCH_PATH= TAG=v1.43.1 fetch_binaries
+  * make TAG=v1.43.1 tarball
+  * make TAG=v1.43.1 sign_upload
+  * make TAG=v1.43.1 check_sign
+  * make TAG=v1.43.1 upload
+  * make TAG=v1.43.1 upload_website
+  * make TAG=v1.43.1 upload_github
+  * NB this overwrites the current beta so after the release, rebuild the last travis build
+  * Announce!