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

[Meta] Create a self serviceable standalone component release process #781

Closed
3 tasks
bbarani opened this issue Oct 21, 2021 · 3 comments
Closed
3 tasks
Labels
enhancement New Enhancement

Comments

@bbarani
Copy link
Member

bbarani commented Oct 21, 2021

Is your feature request related to a problem? Please describe

The current standalone component release process used to release standalone components like Data prepper, OpenSearch clients, SQL drivers etc... is not scalable and self serviceable by the component owners

Describe the solution you'd like

Define the requirements, create a design and implement a repeatable, scalable and self serviceable standalone release process that requires very less manual intervention adhering to OpenSearch release standards.

  • Finalize the requirements
  • Create the design document
  • Implementation

Describe alternatives you've considered

No response

Additional context

Add necessary guard rails to make sure that the self serviceable standalone release doesn't compromise the artifact quality.

@bbarani bbarani added enhancement New Enhancement untriaged Issues that have not yet been triaged labels Oct 21, 2021
@abhinavGupta16 abhinavGupta16 changed the title Create a self serviceable standalone component release process [Meta] Create a self serviceable standalone component release process Oct 26, 2021
@abhinavGupta16 abhinavGupta16 removed the untriaged Issues that have not yet been triaged label Oct 26, 2021
@abhinavGupta16
Copy link
Contributor

[Triaged] Suggestions and comments on the approach to this problem is welcome.

@anirudha
Copy link
Contributor

#794
#795
related older issues

@peternied
Copy link
Member

Closing this this issue is in favor of #1234 that is being actively worked on with deliverables

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

4 participants