Skip to content
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

[META] OpenSearch 3.0 Core Release Tracker #16935

Open
expani opened this issue Jan 2, 2025 · 4 comments
Open

[META] OpenSearch 3.0 Core Release Tracker #16935

expani opened this issue Jan 2, 2025 · 4 comments
Assignees
Labels
Meta Meta issue, not directly linked to a PR untriaged

Comments

@expani
Copy link
Contributor

expani commented Jan 2, 2025

Please describe the end goal of this project

OpenSearch 3.0 will use Lucene 10 in accordance with its release policy of maintaining semver with every major Lucene version release covered more in detail at #250

The published release schedule #252 commits to 17th Feb 2025 as the first alpha release of 3.0

We have upgraded to Lucene 10.1.0 and started using baseline JDK 21 for OpenSearch 3.0 in this PR

The purpose of this meta is to track all the efforts towards releasing OpenSearch 3.0 ( JDK 21/23 + Lucene 10 ) and the order of milestones looks as follows :

Milestone Description Status Issue
1 Efforts to resolve compilation issues caused by removed APIs in Lucene, new methods to override; etc. Completed
2 Efforts to resolve unit and integration test failures ( REST Yaml / InternalCluster / QA ) Completed #16933
3 Efforts to resolve any performance issues that arise with Lucene 10 Upgrade in core OpenSearch. Ongoing #16934
4 Releasing 3.0.0-alpha for plugins to start the same process for themselves to integrate with OS 3.0 Not started
5 Efforts to fix issue in core that arise with plugin integrations after Lucene 10 Upgrade. Not started

Issues

Contribution

If you wish to contribute by fixing a failing test in #16366 please drop a message on the PR with the test you are planning to pick so that others can focus on different one's.

Create a PR against the issue-11415 branch in reta's fork. Link this meta on the PR as well.

If it's a very involved test failure or a change that needs to be on the radar for Performance runs, make sure to create an issue and link with this meta.

We will keep posting messages for help required in contributions with title Help Needed - Testing/Performance

These will be tests or issues that primary owners don't have bandwidth to actively look into for sometime.

Stakeholder Notifications

We will send weekly updates on this meta on the progress towards alpha release candidate readiness of OpenSearch core.

Look out for messages with title ALPHA OS 3.0 RC - CORE READINESS STATUS

This will contain the number of tests fixed, highlight significant changes and capture any callouts for performance runs.

Supporting References

Lucene 10 Update Feature Request

Baseline JDK 21

Breaking Changes in OpenSearch 3.0

Related component

Other

@expani expani added Meta Meta issue, not directly linked to a PR untriaged labels Jan 2, 2025
@expani
Copy link
Contributor Author

expani commented Jan 2, 2025

ALPHA OS 3.0 RC - CORE READINESS STATUS

Milestone-2 Completed - Unit and Integration tests are passing in OpenSearch with Lucene 10 changes.

Milestone-3 Ongoing

@andrross
Copy link
Member

andrross commented Jan 7, 2025

@expani @getsaurabh02 This issue appears to be focused on the Lucene 10 upgrade in core. There are a few other significant things that have been discussed for 3.0 in core, namely resolving top level package split across modules (#8110) and removal of all deprecated code (much of this around inclusive naming, such as #5214). Should we formalize that list of work and track progress here as well?

@expani
Copy link
Contributor Author

expani commented Jan 7, 2025

@andrross Was planning to close this once we have OS 3.0 released.
Will the linked feature requests/Meta need to be completed before OS 3.0 release ?

@andrross
Copy link
Member

andrross commented Jan 7, 2025

Was planning to close this once we have OS 3.0 released. Will the linked feature requests/Meta need to be completed before OS 3.0 release ?

@expani Yes, breaking changes by definition must go in before the 3.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta Meta issue, not directly linked to a PR untriaged
Projects
Status: New
Development

No branches or pull requests

2 participants
  NODES
COMMUNITY 2
INTERN 1
Project 9
USERS 1