-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release of Che 7 Beta #12621
Comments
no issue on my side |
What happens if we need to do a che 6.20 or other future 6.x maintenance between now and August 2019? Would that be done in the 6.19.x branch? Or... do we need a 6.x branch in addition to 6.19.x and master branches. Also, 7.0.x-Beta1 sounds like an odd way to branch - that implies the next build will be 7.0.1.Beta1. Should we have a 7.0.0.Beta1x branch instead, in case we need to do a 7.0.0.Beta1-1 ? -1 for this plan. Suggest we need instead 2 tags and 4 branches:
|
In what circumstances should we need a version
Yes if we will need a
You are right. Calling the branch |
After looking at https://semver.org/#spec-item-9 I think we should call the version |
+0, What about something simpler like +1, If we're happy doing all future maintenance in 6.19.x branch, then I'm happy to not need a 6.x branch. |
@nickboldt I am ok with @riuvshin I would apreciate if you could provide you opinion on this approach. |
done |
Description
At the end of next sprint (in 3 weeks) we should release 2 versions/branches:
6.19.0
/6.19.x
and7.0.0-beta.1.0
/7.0.0-beta.1.x
. Master branch should than use version7.0.0-beta.2.0-SNAPSHOT
and in branch6.19.x
we should only commit/cherry pick Che 6 fixes.@riuvshin @benoitf @nickboldt what do you think?
The text was updated successfully, but these errors were encountered: