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

[Proposal] Improve OpenSearch release process #2080

Open
bbarani opened this issue May 3, 2022 · 1 comment
Open

[Proposal] Improve OpenSearch release process #2080

bbarani opened this issue May 3, 2022 · 1 comment
Labels
enhancement New Enhancement

Comments

@bbarani
Copy link
Member

bbarani commented May 3, 2022

Is your feature request related to a problem? Please describe

The current release process has lot of manual overhead and needs to be automated to support minor and patch version(s) for multiple major versions.

Describe the solution you'd like

  1. Patch release for current / previous major versions:

    1. Patch release should follow a completely automated release process with a pre-defined cadence. This will be a set it and forget it (SiFi) pipeline that will build, test and publish the patched artifacts automatically. The patch release workflows would automatically start building the artifacts against the last minor version of a major on the pre defined cadence (once / twice a month) and executes the tests and publish the patched artifacts to the target distribution channels on the release day. The workflows would standardize the red, yellow and green criteria and send notifications at a periodic cadence to stakeholders and track a given release end to end.
  2. Minor release for current version:

    1. Minor release should follow one click release model where all the artifacts will be staged and ready to be deployed to production by click of a button. The workflows would standardize the red, yellow and green criteria and send notifications at a periodic cadence to stakeholders and track a given release end to end.
  3. Major release for next version:

    1. Major release should follow one click release model where all the artifacts will be staged and ready to be deployed to production by click of a button. The workflows would standardize the red, yellow and green criteria and send notifications at a periodic cadence to stakeholders and track a given release end to end.

Describe alternatives you've considered

No response

Additional context

(#1361)
(#4216)

@bbarani bbarani added enhancement New Enhancement untriaged Issues that have not yet been triaged labels May 3, 2022
@bbarani
Copy link
Member Author

bbarani commented May 6, 2022

[Triage] This is a north star vision that requires automating the release process along with the tasks involved for release activities. We need to closely work with all the teams to achieve this goals.

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

No branches or pull requests

1 participant