Skip to content
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 #94

Closed
Tracked by #142
prudhvigodithi opened this issue Jul 15, 2022 · 8 comments
Closed
Tracked by #142

Implement OpenSearch core branching strategy #94

prudhvigodithi opened this issue Jul 15, 2022 · 8 comments
Assignees
Labels
enhancement New feature or request v2.2.0

Comments

@prudhvigodithi
Copy link
Member

Description

Ensure MAJOR_VERSION.x branch exists, the main 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 ISSUE

Proposed solution

Follow OpenSearch core branching. Create 1.x and 2.x branches, do not create 2.0 as a branch of main, instead create main -> 2.x -> 2.0. Maintain working CI for 3 releases at any given time.

@prudhvigodithi
Copy link
Member Author

prudhvigodithi commented Jul 28, 2022

Hey @vamshin @VijayanB can you please post an update and make the necessary changes to align with core branching strategy.
Thank you
@dblock @bbarani @CEHENKLE

@navneet1v
Copy link
Collaborator

navneet1v commented Jul 29, 2022

@prudhvigodithi The branching strategy has been implemented, I can see main pointing to 3.0, 2.x pointing to latest 2.2 release.. We don't have 1.x, 2.0 and 2.1 branches as this repo was not launched at that time. Please provide details what else is missing.

@navneet1v
Copy link
Collaborator

@VijayanB can you please check if there is any action item left on this?

@VijayanB
Copy link
Member

VijayanB commented Aug 3, 2022

Following core's branching strategy. No action is required.

@VijayanB VijayanB closed this as completed Aug 3, 2022
@dblock
Copy link
Member

dblock commented Sep 29, 2022

Could you please double-check that:

@navneet1v
Copy link
Collaborator

navneet1v commented Sep 30, 2022

Tasks completed

@navneet1v
Copy link
Collaborator

As per the latest update, 2.3.1 release is not happening. So I won't do the version update. Will work on adding this repo in the 3.0 and 2.4 manifest files.

@navneet1v
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v2.2.0
Projects
None yet
Development

No branches or pull requests

5 participants