-
Notifications
You must be signed in to change notification settings - Fork 275
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
Git branching model #4433
Comments
What should be done with |
it's going to be removed. We will have |
Pay attention that i2 CI has several important bindings with branch names (triggers, image tag names...). So, please describe a possible images naming policies changes here or somewhere else. |
What if we make |
yeah, I was thinking about this and I'm leaning to agree with this even though it's not what GitFlow recommends. We don't need
The workflow would then be as follows:
|
we don't even need |
done |
regarding git branching model. I think we should make the following sequence of steps:
main
to a new branchiroha1-main
iroha2-stable
contents tomain
branchdevelop
branch to a new branchiroha1-develop
iroha2-dev
contents todevelop
branchstable
branch and copy contents ofiroha2-stable
into itiroha2-
prefixThe workflow would then be as follows:
develop
branch and merge all new features into itdevelop
intomain
(this is a followed by a release announcement)main
intostable
The text was updated successfully, but these errors were encountered: