Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documented release process for CQF Tooling packages #315

Merged
merged 2 commits into from
Nov 12, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down