Support minor release on release branch #5946
jackye1995
started this conversation in
Ideas
Replies: 1 comment
-
|
implementation: #5949 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Since we switched to semantic versioning, we have had 2 major releases and multiple patch releases, things have been stablized and streamlined at this point.
Currently the main problems I see are that:
Based on the community sync discussion, I propose that we learn from projects like DataFusion and allow releasing a minor version in a release branch. The new rules are the following:
Example 1:
Currently we have released version
2.0.0. The main branch is at2.1.0-beta.1(no new breaking changes has happened). Then we will just cut 2.1 release from main branch. This would create arelease/v2.1branch rooted from the latest main branch commit.Example 2:
Currently we have released version
2.0.0. The main branch is at3.0.0-beta.1(some new breaking changes has happened). Then if we want a new release before 3.0.0 release, we will backport the PRs needed torelease/v2.0and then cut a 2.1.0 release onrelease/v2.0. This would create arelease/v2.1branch rooted from the latestrelease/v2.0branch commit.Note that this is a proposal for release process change in lance repo, I don't think it requires a vote, but if we agree on this direction, I will submit a PR around it.
One open question: currently we require 3 day voting period for minor release. If the goal here is to get a stable release out more quickly, would it make more sense to reduce the voting period to something like 1 day? (if we want to change this, it would require a vote in PMC private list since it changes the governance document itself)
Beta Was this translation helpful? Give feedback.
All reactions