-
Notifications
You must be signed in to change notification settings - Fork 277
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
[RELEASE] Release version 1.3.1 #1805
Comments
@gaiksaya I don't see the component issues created yet. Should we wait for those issues to be created or should we follow another plan? |
@DarshitChanpura Patch releases follow light weight process. We will cut component issues only for the impacted plugins. |
Release testing
From Docker Release |
X64 integ-test:
Anomaly detection failure:
Index management failure:
|
ARM64 tests:
|
OpenSearch Dashboards (Integ Tests x64 - with-security)Re-run all tests pass
OpenSearch Dashboards (Integ Tests x64 - without-security)Re-run 3:
Re-run 2:
Re-run 1:
OpenSearch Dashboards (Integ Tests arm64 - with-security)
OpenSearch Dashboards (Integ Tests arm64 - without-security)
|
Reran X64 tests looks like tests were flaky. Everything looks good now:
|
All the post release activities have been completed. closing this issue. |
I see tags, but don't see 1.3.1 releases anywhere on GitHub, checked https://github.com/opensearch-project/OpenSearch/, https://github.com/opensearch-project/common-utils, https://github.com/opensearch-project/job-scheduler, ... Note that https://github.com/opensearch-project/common-utils doesn't have a 1.3.0 release either. |
The release notes, https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-1.3.1.md only mention 1 plugin, including a version bump in it, but no version bump changes in any other plugins/no release notes for them? See opensearch-project/OpenSearch#2699 (comment): Expected: Versions are consistent on website, github, docker, etc and there are changenotes and a news item on the website on the focus of the release. |
@dblock We do not add all the version bump related notes to the consolidated release notes for patch releases. We only add the release notes of the plugins that had changes. |
That's fair, I was just confused because 1 plugin had that in the release notes, and the others didn't. I am still confused :) |
@gaiksaya Care to comment on #1805 (comment)? |
The automated tagging tool currently creates tags only but we will enhance it to create releases as well. Also, the teams doesn't seem to follow the process of creating releases prior to automating tag creation process as well. They were only creating tags manually after releases and not releases itself (Ex: https://github.com/opensearch-project/index-management/releases) |
We have created issue to address the above releases on GH concern: #1898 |
Closing this issue now. |
Release OpenSearch 1.3.1
I noticed that a manifest was automatically created in manifests/1.3.1. 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.Create a release issue in every component repo that links back to this issue, update Components section with these links.We are taking care of everything for this patch releaseEnsure that all release issues created above are assigned to an owner in the component team.CI/CD (Feature Freeze) - March 28 2022
Campaigns
REPLACE with OpenSearch wide initiatives to improve quality and consistency.
Code Complete - March 28 2022
Release testing - March 29 2022
Performance testing validation - Ends REPLACE_RELEASE-minus-6-days
Performance tests do not show a regressionLongevity tests do not show any issuesRelease - March 30 2022
v1.3.1
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: