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

How to anticipate the correct release branch name? #1

Open
jdimeo opened this issue Feb 21, 2022 · 0 comments
Open

How to anticipate the correct release branch name? #1

jdimeo opened this issue Feb 21, 2022 · 0 comments

Comments

@jdimeo
Copy link

jdimeo commented Feb 21, 2022

If we're using semver for branch names, how do you know exactly if your work for that release will be patch vs. minor vs. major? For example, I might be planning on 1.0.5 but then due to shifting priorities or an angry customer, we squeeze in an API contract change and it needs to become 1.1.0.

I suppose the answer is you just start a 1.1.0 branch and merge the dead branch in, but I'm wondering if that creates more noise in real world applications of this branching model.

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

No branches or pull requests

1 participant