[PROPOSAL] Standardize branching strategy

[andrross]

The OpenSearch project generally follows a strategy of tracking 3 releases in parallel (next major, next minor, and current). See RELEASING.md for more details. This repository currently only has a main branch that is targeting version 1.2.4. Should we update to match the OpenSearch branching strategy. If not, why not?

Assuming the answer is yes, then the steps are (I think?):

• Create branch 1.2, which will be the current commit on main, supporting version 1.2.4
• Create branch 1.3 and implement support for version 1.3.8
• Create branch 2.x and implement support for 2.6.0
• Implement support for 3.0.0 on main

[anasalkouz]

@dblock or @samuel-oci not sure if you have some context on this repository
Is any reason why it is not following OpenSearch branching strategy?
Why it's not part of the OpenSearch release bundle?

[wbeckler]

I propose that this entire repo be moved here: https://github.com/opensearch-project/OpenSearch/tree/main/plugins in a subdirectory called "repository-oci," just like there is a repository-azure and a repository-s3. If not, then why not create repos for those other cloud file stores?

[wbeckler]

I've opened an issue suggesting this: opensearch-project/OpenSearch#6148

[sam-herman]

Hi @anasalkouz @andrross @wbeckler , some context:
Originally it was created as a separate repo in order to allow the community time to decide how to address object storage repository plugins in the community. The community feedback at the time was captured here:
opensearch-project/OpenSearch#1854

I agree with @wbeckler suggestion, I think that moving it into the core for now will probably make sure it remains consistent with both versioning strategy and will make routine maintenance and upgrade efforts easier.

[sam-herman]

Regarding the branching strategy, if we want to take more time before moving it into the core, using a proper conventional branching strategy can't hurt.

[sam-herman]

I created a 1.3 branch from the current commit on main. After merging #33 I will create a 2.4 branch.
Going forward will keep the above branching strategy after any version upgrade. Closing this for now while the suggestion to move to the monolith is discussed here: https://github.com/opensearch-project/OpenSearch/tree/main/plugins.