-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release documentation update #218
Conversation
…links to create and view issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I updated the homepage and footer with items discussed in the touchpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, just a few minor wording tweaks
README.md
Outdated
This repository will leverage a branching strategy to maintain multiple versions of opioid recommendations (currently 2016 and 2022) and their respective IG's. This will use semantic versioning on releases to make it clear which version of the recommendations the release is for. Any release for 2022 version will be v2022.#.# and any that are 2016 will be v2016.#.#. | ||
This repository will leverage a branching strategy to maintain multiple versions of the CDC opioid recommendations (currently 2016 and 2022) and their respective IG's. This will use semantic versioning on releases to make it clear which version of the recommendations the release is for. | ||
The format used will be major.minor.patch | ||
- major is for new CDC Recommendations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider: major is used to refer to the guideline publication year (e.g. 2016)
This answers issue #216 first point:
Would be good to explain the significance of the minor and patch versions:
major: Guideline version
minor: New features and capabilities, but not breaking changes
patch: Bug fixes and technical corrections.
Would be good to illustrate that in the diagram with a 2022-Fix branch and 2016-Fix branch showing the version increment
Snd the point:
For 2022, the IG and all the artifacts in it are "draft" status.
For 2016,, the IG is active, and any artifact we have pilot experience with is "active", all the rest are "draft"
Other parts of the issue forthcoming.