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
Question: What is the purpose/meaning/workflow of the release/v0.18
branch?
#3602
Comments
release/v0.18
branch?release/v0.18
branch?
This comment was marked as abuse.
This comment was marked as abuse.
I'm also confused by this, the difference is bigger now: This branch is 32 commits ahead of, 46 commits behind main. did main and the v0.18 branch diverge and meant to stay that way, or why is it not merged back? Hard to tell which branch to keep track of |
It looks like the same changes are independently being applied to both branches ( |
The cargo package versions seem to be lagging way behind indeed (are the commits updating them not applied?). But the reason your server is identifying itself as 0.18.1 is probably that the latest tag in the main branch is 0.18.1-rc.10 and the version is set by the latest tag in the branch (+ commit hash) in the dockerfile - and while the latest commits seem to have been applied, the tags are missing |
This comment was marked as abuse.
This comment was marked as abuse.
That was to be expected, since it was done similarly with the 0.17.x (and earlier) releases. What I still don't get is, why @dessalines Can you shed some light on what the branch strategy is for this project or rather point us to some documentation? Thanks. |
We use stable mainline on all our repos. |
This comment was marked as abuse.
This comment was marked as abuse.
Then it seems that I do not understand stable mainline, i. e. I would expect to only see tiny release specific fixes in the release branch and a few cherry-picked fixes which also go into main., since the goal of the release branch is to freeze the code before releasing it. But what I'm seeing is a release branch and main branch running concurrently for quite some time wiith both getting pretty much all changes applied (independently from each other). |
That is exactly what's in the release branch, cherry picked fixes from main, with no breaking changes. main has a lot of breaking changes not in the release branch. Use a git command to compare the commits. |
This comment was marked as abuse.
This comment was marked as abuse.
CI will run for any pushes to other branches, or PRs to any branch. |
Question
0.18.1
which has been tagged inmain
0.18.2
has been tagged in branchrelease/v0.18
RELEASES.md
inmain
has been updated to version0.18.1
RELEASES.md
inrelease/v0.18
is still at version0.17.2
releases/v0.18
is 7 commits ahead ofmain
most of which have matching commits inmain
(just with different hashes). Are these independant commits or does it look like this, if they have been merged frommain
torelease/v0.18
or vice versa, too?releases/v0.18
just a temporary branch which essentially died when version0.18.2
got released or is it meant to stay and tag all version0.18.x
releases?I'm confused.
The text was updated successfully, but these errors were encountered: