-
Notifications
You must be signed in to change notification settings - Fork 4
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
[FEATURE] OpenSearch Project Central Release Dashboard #51
Comments
[Triage] |
Adding a few more to the list:
More to come. Thanks. |
Update: It is easier to use the Therefore I will go ahead and add a few extra information in the report workflow, so @prudhvigodithi can use them directly instead of taking from Jenkins runs:
Thanks. PRs:
|
New functions required:
|
Thanks @peterzhuamazon, the Component repo name should be good and we can generate the repo URL, example |
PR: |
Feature request Details
Use the Metrics Dashboard to track the OpenSearch release progress.
Once all the release details collected with a proper data model these release details can be visualized in the OpenSearch Dashboards which can be utilized by the release manager to oversee the release and serve as a reference point for the audience participating in the release.
What solution would you like?
While we have this Dashboard that can be used during a release that would help the release manager, the following improvements can be added to make the dashboard more informative and can be used to drive the release.
During the release
AUTOCUT
issues per repo.Post Release
Release Retro Meetings
The following data can be utilized in retrospective meetings to review the data points between the RC builds and to develop an action plan for the upcoming releases.
retro
with release version where dashboard shows these issue links and one can discuss these issues in retro meeting.What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: