Add docs for releasing (#16)

* Add docs for releasing

Author: nh13

README.md

@@ -35,4 +35,72 @@ cargo build --release
 ## Developing
 
 fqtk is developed in Rust and follows the conventions of using `rustfmt` and `clippy` to ensure both code quality and standardized formatting.
-When working on fqtk, before pushing any commits, please first run `./ci/check.sh` and resolve any issues that are reported.
+When working on fqtk, before pushing any commits, please first run `./ci/check.sh` and resolve any issues that are reported.
+
+## Releasing a New Version
+
+### Pre-requisites
+
+Install [`cargo-release`][cargo-release-link]
+
+```console
+cargo install cargo-release
+```
+
+### Prior to Any Release
+
+Create a release that will not try to push to `crates.io` and verify the command:
+
+```console
+cargo release [major,minor,patch,release,rc...] --no-publish
+```
+
+Note: "dry-run" is the default for cargo release.
+
+See the [`cargo-release` reference documentation][cargo-release-docs-link] for more information
+
+### Semantic Versioning
+
+This tool follows [Semantic Versioning](https://semver.org/).  In brief:
+
+* MAJOR version when you make incompatible API changes,
+* MINOR version when you add functionality in a backwards compatible manner, and
+* PATCH version when you make backwards compatible bug fixes.
+
+### Major Release
+
+To create a major release:
+
+```console
+cargo release major --execute
+```
+
+This will remove any pre-release extension, create a new tag and push it to github, and push the release to creates.io.
+
+Upon success, move the version to the [next candidate release](#release-candidate).
+
+Finally, make sure to [create a new release][new-release-link] on GitHub.
+
+### Minor and Patch Release
+
+To create a _minor_ (_patch_) release, follow the [Major Release](#major-release) instructions substituting `major` with `minor` (`patch`):
+
+```console
+cargo release minor --execute
+```
+
+### Release Candidate
+
+To move to the next release candidate:
+
+```console
+cargo release rc --no-tag --no-publish --execute
+```
+
+This will create or bump the pre-release version and push the changes to the main branch on github.
+This will not tag and publish the release candidate.
+If you would like to tag the release candidate on github, remove `--no-tag` to create a new tag and push it to github.
+
+[cargo-release-link]:      https://github.com/crate-ci/cargo-release
+[cargo-release-docs-link]: https://github.com/crate-ci/cargo-release/blob/master/docs/reference.md
+[new-release-link]:        https://github.com/fulcrumgenomics/fqtk/releases/new