Describe branch naming conventions #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
explaining the new branch designations for "development" and "release" branches.
kerry-meyer
requested review from
javeedf and
jeff-yin
and removed request for
javeedf
jeff-yin
approved these changes
Jan 21, 2022
These changes eliminate validation sanity faiures by replacing reserved markdown constructs with generic wording.
|
I reviewed the commit and approve of the changes. |
stalabi1
approved these changes
Jan 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Add a note to the "Releasing, Versioning and Deprecation" section of the README file explaining the new branch designations for "development" and "release" branches. This is intended for reference by customers to ensure that they are using only official release versions in production.
ISSUE TYPE
COMPONENT NAME
Repo/branch "README.md" file.
ADDITIONAL INFORMATION
This PR (on the "1.x" branch) is intended for discussion purposes and incorporation of review comments before submitting a PR with the agreed-upon wording for the "main" branch.