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 @praveensameneni @qreshi, can you please post an update and make the necessary changes to align with core branching strategy.
@bbarani @CEHENKLE @bbarani

[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]

@qreshi Are we good to target this change for 2.4.0 release?

[qreshi]

This was blocked for some time since Alerting backend couldn't bump main because Notifications couldn't get to 3.0 without issues. This has since been unblocked so if Alerting backend main is on 3.0, then we should bump Alerting OSD main and then we can close this out.

[bbarani]

@qreshi Can you provide updated status of this issue?

[qreshi]

@lezzago and @AWSHurneyt may have a more up-to-date picture here. I saw that the Alerting backend was bumped to 3.0 yesterday so the frontend will likely soon follow.

[bbarani]

@AWSHurneyt @qreshi Whats the status of this issue?

[AWSHurneyt]

@AWSHurneyt @qreshi Whats the status of this issue?

I believe all that's missing at the moment is that the main branch is not currently set to version 3.0. There were some failures in the bump PR which I have on my tasks list to investigate.

[bbarani]

@AWSHurneyt Can you please provide an update? Were you able to bump the version on main to 3.0?

[AWSHurneyt]

@AWSHurneyt Can you please provide an update? Were you able to bump the version on main to 3.0?

The main branch hasn't been bumped yet, but I'm planning to investigate the blockers for that this sprint.

[AWSHurneyt]

Alerting dashboards main has been bumped to 3.0.