-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
[BUG] develop-6.x.x
is out of sync with 6.3.0 latest release
#5549
Comments
It should not be merged back. As I previously explained to you here and here, if you do that, you will loose context and history and drop some commits. It is a very bad idea to do that! The part of the Contributing to eXist-db document that you sited was written by me and my team. It does not mention release branches (e.g. |
As I see it, a release branch would have been necessary for a v6.2.1 release since new features were introduced to develop-6.x.x. All new features were released with v6.3.0 and the release could have been cut from that branch and we would not have this conversation right now. |
I understood that he was made aware of the fact after the release. So there was no discussion with him nor any other interested party and no peer review. |
@line-o I am trying to help you here to do the release that you want to do without things getting broken. Please try and be constructive and considerate in your tone. |
@adamretter I try to follow the current discussion and getting a bit confused. What exactly is the relation between the |
According to the contribution notes the
develop-6.x.x
is the main branch for ongoing 6.x development.6.3.0
was released from the6.3.0-branch
but we haven't merged back intodevelop-6.x.x
If we want to have a continuous history it should be merge.The text was updated successfully, but these errors were encountered: