diff --git a/Release-Procedure.md b/Release-Procedure.md
index 0498dfe..2d05423 100644
--- a/Release-Procedure.md
+++ b/Release-Procedure.md
@@ -119,4 +119,24 @@ Tweet with the openlayers account, something like: "OpenLayers v3.12.0 is out! T
 ### Notes
 
 <a name="race-condition"></a>
-Note that there is a potential race condition related to creating a changelog before a release is tagged.  This could be avoided by generating the changelog after tagging the release.  However, since we already need to make a change to the repository for the release (updating the version in package.json), the changelog creation step is included with this change for convenience.  There aren't serious consequences associated with missing an entry in the changelog, so this should be an acceptable tradeoff.
\ No newline at end of file
+Note that there is a potential race condition related to creating a changelog before a release is tagged.  This could be avoided by generating the changelog after tagging the release.  However, since we already need to make a change to the repository for the release (updating the version in package.json), the changelog creation step is included with this change for convenience.  There aren't serious consequences associated with missing an entry in the changelog, so this should be an acceptable tradeoff.
+
+### Patch releases
+
+For a patch release, the process is basically the same as for a minor release.  The significant difference is that you want to create a new branch from the minor tag.  For example:
+
+```
+git remote update
+git checkout -b v3.20.1 origin/v3.20.0
+```
+
+Next, you want to cherry pick commits that fix regressions in the minor release.
+
+```
+# for each bug fix commit
+git cherry-pick <SHA_OF_BUG_FIX_COMMIT>
+```
+
+Since the `changelog.sh` relies on merge commits, and there won't be any merge commits between the previous release tag and your patch release branch, you'll need to manually create the changelog.  Copy one of the existing changelogs for a patch release as a starting point.  Link to the pull requests that included the original commits that you cherry picked above.
+
+From this point, you can follow the normal release process ([after the changelog step](https://github.com/openlayers/ol3/wiki/Release-Procedure#update-packagejson)).