docs: add release-process

Author: themightychris

docs/SUMMARY.md

@@ -9,6 +9,7 @@
   - [Data Analysis](contributing/data-analysis.md)
   - [Operations Support](contributing/operations-support.md)
 - Operations
+  - [Release Process](./operations/release-process.md)
   - [The `chime-live` Cluster](./operations/chime-live-cluster.md)
   - [Deploy to Heroku](./operations/heroku.md)
   - [Deploy to Your Own Cluster](./operations/byok8s.md)

docs/operations/release-process.md

@@ -0,0 +1,25 @@
+# Operations: Release Process
+
+1. Merge pull requests into `develop`
+2. Chose a new version number by incrementing the previous release according to [semver](https://semver.org/)
+   - Do not bump the MAJOR version unless the team is ready to create a new `releases/v#` branch
+3. Open a pull request to merge `develop` into `releases/v1`
+   - **Title**: `Release: CHIME v1.#.#`
+   - **Description**: Generate with this command:
+
+        ```bash
+        git fetch origin
+        git log \
+            --first-parent \
+            --reverse \
+            --pretty=format:"- %s" \
+            "origin/releases/v1..origin/develop"
+        ```
+
+4. Get release pull request approved by [`@cjbayesian`](https://github.com/cjbayesian) or [`@mdbecker`](https://github.com/mdbecker)
+5. Merge the pull request
+6. [Create a new release against `releases/v1`](https://github.com/CodeForPhilly/chime/releases/new?target=releases/v1)
+   - **Tag version:** `v1.#.#`
+   - **Release Title:** `CHIME v1.#.#`
+   - **Description:** Copy release notes from pull request
+7. [Deploy to the `chime-live` cluster](chime-live-cluster.md)