Update CI to Handle No dev Branch
#9
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
jharajeev55
previously approved these changes
Mar 29, 2024
jharajeev55
previously approved these changes
Mar 29, 2024
jharajeev55
approved these changes
Apr 1, 2024
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.
To simplify the release workflow, the team has decided to remove the
devbranch. This change requires a few changes to the CI system for all projects.main, create an appropriately versioned RC release (a tag, a GitHub release, plus any packaging) with the version indicated by the project's manifest file followed by a-N, whereNis an incrementing number based on the number of RC tags for that release already in existence.mainis a release branch, create an RC for every push to that branch with the version indicated by the release branch name followed by a-N, whereNis an incrementing number based on the number of RC tags for that release already in existence.mainfrom a release branch, create a full release with the version number indicated in the release branch name.