Update contributing file

Author: jmdobry

CONTRIBUTING.md

@@ -23,3 +23,17 @@ When submitting issues on GitHub, please include as much detail as possible to m
 1. The `dist/` folder & files will be generated, do NOT commit `dist/*`! They will be committed when a release is cut.
 1. Submit your PR and we'll review!
 1. Thanks!
+
+#### Have write access?
+
+Here's how to make a release on the `master` branch:
+
+1. Bump `package.json` to the appropriate version.
+1. `npm test` must succeed.
+1. This time, the built `dist/js-data-sql.js` file _will_ be committed, so stage its changes.
+1. Mention the release version in the commit message, e.g. `Stable Version 1.2.3`
+1. Push to master.
+1. Create a git tag. Name it the version of the release, e.g. `1.2.3`
+  - Easiest way is to just create a GitHub Release, which will create the tag for you. Name the Release and the git tag the same thing.
+1. `git fetch origin` if you tagged it via GitHub Release, so you can get the tag on your local machine.
+1. `npm publish .` (Make sure you got the version bumped correctly!)