Merge pull request #315 from cqframework/feature-document-release-pro…

…cess

Documented release process for CQF Tooling packages

README.md

@@ -42,6 +42,19 @@ Changes to the `master` branch must be done through an approved PR. Delete branc
 
 Merges to `master` trigger a deployment to the Maven Snapshots repositories. Once ready for a release, the `master` branch is updated with the correct version number and is tagged. Tags trigger a full release to Maven Central and a corresponding release to Github. Releases SHALL NOT have a SNAPSHOT version, nor any SNAPSHOT dependencies.
 
+## Release Process
+
+To release a new version of the tooling:
+1. Update master to be a release version (and all the reviews, bug fixes, etc. that that requires)
+   1. Regression test against IGs known to use CQF Tooling
+2. Passed Travis Build = ready for release
+3. Create a Github Release (which creates a tag at the current commit of master)
+   1. Choose the "Auto-generate release notes" option
+4. Travis does the release to Maven
+   1. Ensure binaries are published to https://oss.sonatype.org/#view-repositories;public~browsestorage~org/opencds/cqf/tooling 
+5. Update master to vNext-SNAPSHOT
+6. Close all issues included in the release
+
 ## Getting Help
 
 Bugs and feature requests can be filed with [Github Issues](https://github.com/cqframework/cqf-tooling/issues).