Release-process-checklist.md

@@ -2,7 +2,7 @@
 
 * [For regular releases](https://github.com/mathjax/MathJax/wiki/Release-process-checklist#for-releases)
 * [For beta releases](https://github.com/mathjax/MathJax/wiki/Release-process-checklist#for-beta-releases)
-* [For hotfix releases](https://github.com/mathjax/MathJax/wiki/Release-process-checklist#for-hotfix-releases)
+* [For patch releases](https://github.com/mathjax/MathJax/wiki/Release-process-checklist#for-patch-releases)
 
 ## For regular releases
 
@@ -71,22 +71,21 @@ This is almost identical, except that we don't do as much.
 * The new post should be announced on social media channels [[MathJax-web-presence]].
 
 
-## For hotfix release
+## For patch release
 
-This is the process for releasing a hotfix to the CDN:
+This is the process for releasing a patch release to the CDN:
 
-1. Prepare and test a branch with the fixes as per our regular development process
-2. Merge to master and the release branch at GitHub, e.g v1.1-latest
-1. Copy the release branch to `mathjax/x.y-beta` on Cloud Files
-1. Test
-1. Announce it so people can test against it
-1. Send warnings to the cdn-notify list 72 hours in advance 
-1. Sync the new release to `mathjax/x.y-latest` and `mathjax/latest` on Cloud Files (e.g., Cyberduck can sync folders). Note: renaming/deleting folders on Cloud Files is much slower than syncing. 
-1. File ticket with Rackspace to purge the container; this will take 24h-48h.
-1. Send confirmation to the cdn-notify list, and update the download page at mathjax.org
+1. Prepare and test a `vN.m.x` branch with the fixes as per our regular development process
+2. Merge to vN.m-latest (and master when patching the current release).
+3. Tag / make a GitHub release pointing to milestone.
+1. Copy the changed files to `mathjax/x.y-latest` (and `mathjax/latest` if that's the latest) on the CDN
+1. Purge the CDN
+1. Send email update to sponsors, mailing lists, cdn-notify list
 1. Monitor for any issues.
 
-Note that our policy is that we don't tag and package the hot fixes separately. Thus, for example, the v1.1 archive is always the initial v1.1 release, and access to updates for your own server would be through git (by checking out the v1.1-latest branch, which already exists, and will contain the hot fixes), or through the GitHub interface by selecting the v1.1-latest branch in the branch list and then using the Download button there to get the automatically packaged copy. From the [documentation](http://www.mathjax.org/docs/1.1/installation.html#obtaining-mathjax-via-an-archive):
+Note that our policy is that we don't create tracking branches or documentation branches for patch releases. 
+
+From the [documentation](http://www.mathjax.org/docs/1.1/installation.html#obtaining-mathjax-via-an-archive):
 
 > If a packaged release receives any important updates, then those updates will be part of the branch for that version. The link to the .zip file in the download list will be the original release version, not the patched version. To obtain the patched version, use the Branches drop down menu (at the far left of the menus within the page) to select the release branch that you want (for example v1.1-latest), and then use the download button and the Download .tar.gz or Download .zip button to get the latest patched version of that release.