Implement OpenSearch core branching strategy

[prudhvigodithi]

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]

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

[ankitkala]

We're following the branching strategy. However main is not on 3.0 as security plugin is still not on 3.0.
Tracking issue: opensearch-project/security#1953

[dblock]

The job-scheduler issue was fixed, see opensearch-project/job-scheduler#242.

[dblock]

There should be nothing blocking this rn. To close this issue:

• main is building 3.0
• 2.x is building next 2.x, which is currently 2.4.0
• 2.3 is building next 2.3, which is 2.3.1
• manifests in https://github.com/opensearch-project/opensearch-build/tree/main/manifests include all 3

[bbarani]

@ankitkala Re-tagging this issue to v2.4.0

[ankitkala]

Closing the issue as all tasks have been addressed.

[krishna-ggk]

Reopening - should we keep this open until we automate it? (For example 2.x should now be tracking 2.5)

[ankitkala]

Closing this for now. bump up on 2.x depends on security plugin.