-
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 2.0.0 (RC1) #1624
Comments
[Triage] @bbarani please advice on the release timing and I will then send out the release issues to plugin owners of 2.0.0. Thanks. |
@peterzhuamazon Please start sending the release issues to the plugin owners repo as soon as possible as this is a Major release and its better to start building the distribution to surface any potential gaps. |
That works even better! Thanks for confirming that. |
RPM:
|
|
RPM OS x64 + OSD x64
|
RPM OS arm64 + OSD arm64
|
Hey. We discovered a problem last night with PA and RPM. We're currently evaluating, but if we need to rebuild, it would push us off Thursday as a release date to (likely Tuesday). Please feel free to chime in on the issue, and if we do move the date to accommodate, we'll update here. |
@peterzhuamazon I've created #2046 for retro items |
Based on the time needed to retest to fix #2043 we'll be moving the release date of 2.0 RC1 to Tuesday May 3rd (updating this ticket, roadmap and blog post now). We may need to move out the full 2.0 release date if we think that's not going to be enough time to get feedback, so please let us know. Please leave your feedback here on that issue. Thanks! |
BTW for some context on the 2.0-RC and 2.0 window. With the RC date moved, but the full release not moved, things look like this:
Moving the release date to for RC-1 to May 3rd puts the freeze date for GA the day BEFORE the release. I propose we shift GA out a week to:
I've moved the Freeze Date out 15 days, and the release date out 12 days. I think having more time to have the RC out in the wild is more important than a longer freeze date. WDYT? |
Current OSD 2.0.0-rc1 bwc test (no security plugin)
|
@CEHENKLE , Data Prepper 1.4 is releasing on May 10 and it will need the 2.0.0-RC1 client to be compatible with OpenSearch 2.0 clusters. The May 3rd release date for 2.0.0 RC1 works for this, but pushing it back further would risk OpenSearch 2.0 compatibility in Data Prepper 1.4. |
@dlvenable Sounds like you may need a 1.5? |
That may be necessary if the Maven artifacts are not available in time for our release. If the 2.0.0-rc1 client is available in Maven this week though, we can use it in Data Prepper for the 1.4 release. Broadly speaking I was expressing a favorable vote for putting RC1 out sooner in response to:
|
Data Prepper already has a 1.5 scheduled. But, we had hoped to have the 2.0.0 support available in 1.4 prior to the release of OpenSearch 2.0.0 GA. |
Native Plugins:
|
Release OpenSearch and OpenSearch Dashboards 2.0.0 (RC1)
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
__REPLACE_RELEASE-__
placeholders have actual dates.CI/CD (Feature Freeze) - 2022/03/21
Campaigns
Code Complete - 2022/03/22 - 2022/04/18
Release testing - 2022/04/19 - 2022/04/21
Performance testing validation - 2022/04/19 - 2022/04/22
- [ ] Longevity tests do not show any issuesRelease -
2022/04/25 - 2022/04/26~~ 2022/04/27 - 2022/04/28~~ 2202/5/02 - 2022/05/03v2.0.0
in all projects have been resolved.Post Release
rc1
qualifiers from2.0
branch #2078Components
Overall status: Post Release 2.0.0 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/02
Legend
| Symbol | Meaning | | -------- | ---------- | | 🟢 | On track with overall release | | 🟡 | Missed last milestone | | 🔴 | Missed multiple milestones |
Issue tracking (Updated 2022/05/02 17:42PST)
Issues:
latest
url referring to in ci.opensearch.org #1973MODULE_NOT_FOUND
notifications#410Improvements:
rc1
qualifiers from2.0
branch #2078The text was updated successfully, but these errors were encountered: