-
Notifications
You must be signed in to change notification settings - Fork 141
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
Implement OpenSearch core branching strategy #692
Comments
@prudhvigodithi I'm currently aligning 1.x and 2.x branches. Do we have to update main to 3.0? |
Updated 1.x and created 2.x from main. @prudhvigodithi please feel free to re-open the issue, if the main needs to be updated to 3.0 |
@prudhvigodithi waiting for ml-commons to merge in 3.0 |
Closed the PR for bumping main branch to 3.0, for now. Will reopen once we have decision opensearch-project/opensearch-plugins#142. Let's keep this issue open. |
Try to upgrade main to 3.0 failed. #831.
|
The job-scheduler issue was fixed, see opensearch-project/job-scheduler#242. |
|
To close this issue:
|
2.3.1. #894 |
manifest PR. opensearch-project/opensearch-build#2766 |
@penghuo Updating the tagged version for this issue to 2.4.0 |
Description
Ensure
MAJOR_VERSION.x
branch exists, themain
branch acts as source of truth effectively working on 2 versions at the same time.Related META issue
opensearch-project/opensearch-plugins#142
Current Behavior
Currently plugins follow a branching strategy where they work on
main
for the next development iteration, effectively working on 2 versions at the same time. This is not always true for all plugins, the release branch or branch pattern is not consistent, the lack of this standardization would limit multiple automation workflows and alignment with core repo. More details on META ISSUEProposed solution
Follow OpenSearch core branching. Create
1.x
and2.x
branches, do not create2.0
as a branch of main, instead createmain -> 2.x -> 2.0
. Maintain working CI for 3 releases at any given time.The text was updated successfully, but these errors were encountered: