Prepare for release v0.2.0

Signed-off-by: Matt Butcher <matt.butcher@fermyon.com>

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "bartholomew"
-version = "0.1.0"
+version = "0.2.0"
 edition = "2018"
 
 [dependencies]

release-process.md

@@ -0,0 +1,16 @@
+# Cutting a Bartholomew Release
+
+To cut a release of Bartholomew, you will need to do the following:
+
+1. Create a pull request that changes the version number for your new version (e.g. 1.2.2 becomes 1.2.3)
+    - `Cargo.toml` is the most important place to make this change
+    - Check the docs for hard-coded version strings
+2. Merge the PR created in #1 (Such PRs are still required to get approvals, so make sure you get signoff on the PR)
+3. Create a new tag with a `v` and then the version number (`v1.2.3`)
+4. Push the tag up to `main` on GitHub
+    - This will trigger a release build
+5. Wait for the `release` [action](https://github.com/fermyon/bartholomew/actions/workflows/release.yaml) to complete, and download the binary artifacts that are generated by that action.
+6. Generate SHAs of the Windows, Mac, and Linux binaries with `shasum` or a similar command
+7. Go to the GitHub [tags page](https://github.com/fermyon/bartholomew/releases) and create a release, adding release notes, and uploading the binaries you downloaded above. The SHAs should go in the release notes.
+
+At this point, you can just verify that all things are good.