-
Notifications
You must be signed in to change notification settings - Fork 272
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 2.0.0 #2086
Comments
There was a config change within the test setup infrastructure which led to the deviations in the results above.
2.0.0 compared to 1.3.2 -
|
RPM Validation:
|
The test of AD Dashboards is flaky due to all integTest dashboards is running in the same container, we should expand the integTest dashboards just like integTest opensearch to run parallel in separate containers for each plugin: Here is the test running in the same docker image with the same method in Jenkins and success:
|
Test OBS:
|
|
All other integTest pass with green state. |
The release is currently on hold due to last minute issue. Please follow this forum thread for current updates. |
We will be releasing OpenSearch 2.0 GA version on May 26 2022. |
|
|
We have issues releasing maven as sonatype is not able to communicate with server. Thanks. |
We have opened an issue with Sonatype as it is still not resolved: |
I see |
Give it 1+ hrs sonatype use a cron to sync so wont be that fast 😄 Thanks. |
The maven link should work now. :D |
Release OpenSearch and OpenSearch Dashboards 2.0.0
I noticed that a manifest was automatically created in manifests/2.0.0. 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
2022/05/17
is pencils down date for feature freeze.__REPLACE_RELEASE-__
placeholders have actual dates.CI/CD (Feature Freeze) - 2022/05/04 to 2022/05/17
Campaigns
rc1
qualifiers from2.0
branch #2078Code Complete - 2022/05/04 to 2022/05/17
No More Changes commited to 2.0 branch
): Make sure that the code for this specific version of the release is ready and the branch corresponding to this release has been added to this release version manifest.Release testing - 2022/05/18 to 2022/05/20
Performance testing validation - 2022/05/18 to 2022/05/20
Release - 2022/05/23 to 2022/05/24
v2.0.0
in all projects have been resolved.2022/05/23
- Publish this release on opensearch.org.2022/05/24
- Publish a blog post - release is launched!Post Release
2.0.0
release.2.0.0
release.Components
Overall status: Post Release 2.0.0 GA has been released, all post release tasks should be worked on and component release tasks closed out.
Next Step: Closing this release task, ETA 2022/05/24
Legend
Issue tracking (Updated 2022/05/23 14:07 PST)
General Issues:
api/status
api/reporting/stats
route authentication addition in future releases #2112could not find java in JAVA_HOME at /opt/java/openjdk-17/bin/java
#2120IntegTest Related Issues
Improvements:
The text was updated successfully, but these errors were encountered: