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

Add Release Docs #183

Merged
merged 1 commit into from
Jan 4, 2024
Merged

Add Release Docs #183

merged 1 commit into from
Jan 4, 2024

Conversation

mckadesorensen
Copy link
Contributor

No description provided.

README.md Outdated Show resolved Hide resolved
@mckadesorensen mckadesorensen merged commit df8de10 into master Jan 4, 2024
2 checks passed
Comment on lines +34 to +35
A release branch should be created when backporting a feature, such as `release/v17.1.4.2`.
In this case, the release branch `release/v17.1.4.2` should be created from the tag `v17.1.4.1`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you'd want to include the CIRRUS version in the release branch name. You probably don't need the entire cumulus version either. It makes more sense to me to have a release/v17 branch that you make tags off of just like you would with master for the latest releases. That way you can maintain that branch as long as that cumulus version needs to be supported, and if there are updates to cumulus you can pull those in without creating inconsistencies with the branch name.

No reason why for backports you need to create a separate branch for every release, that's what tags are for.

@mckadesorensen mckadesorensen deleted the dms/update/docs branch February 27, 2024 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants