You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release OpenSearch and OpenSearch Dashboards 1.2.5
I noticed that a manifest was automatically created in manifests/1.2.5. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers Release owner section.
Release Steps
There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release. The release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.
Component List
To aid in understanding the state of the release there is a table with status indicating each component state. This is updated based on the status of the component issues.
Preparation
Assign this issue to a release owner.
Declare a pencils down date for new features to be merged. _REPLACE_RELEASE-minus-14-days is pencils down.
Update the Campaigns section to include monitoring campaigns during this release.
Update this issue so all __REPLACE_RELEASE-__ placeholders have actual dates.
Document any new quality requirements or changes.
Declare a pencils down date for new features to be merged.
Code Complete (REPLACE_RELEASE-minus-14-days - REPLACE_RELEASE-minus-11-days): Teams test their component within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
Sanity Testing (REPLACE_RELEASE-minus-8-days - REPLACE_RELEASE-minus-6-days): Sanity testing and fixing of critical issues found by teams.
Release - _Ends {_REPLACE_RELEASE-day}
Declare a release candidate build, and publish all test results.
Release OpenSearch and OpenSearch Dashboards 1.2.5
I noticed that a manifest was automatically created in manifests/1.2.5. Please follow the following checklist to make a release.
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. More details are included in the Maintainers Release owner section.
Release Steps
There are several steps to the release process, these steps are completed as the whole release and components that are behind present risk to the release. The release owner completes the tasks in this ticket, whereas component owners resolve tasks on their ticket in their repositories.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release.
Component List
To aid in understanding the state of the release there is a table with status indicating each component state. This is updated based on the status of the component issues.
Preparation
__REPLACE_RELEASE-__
placeholders have actual dates.CI/CD - Ends REPLACE_RELEASE-minus-14-days
Campaigns
REPLACE with OpenSearch wide initiatives to improve quality and consistency.
Release testing - Ends REPLACE_RELEASE-minus-6-days
Release - _Ends {_REPLACE_RELEASE-day}
v1.2.5
in all projects have been resolved.Post Release
Components
Replace with links to all component tracking issues.
Legend
The text was updated successfully, but these errors were encountered: