-
Notifications
You must be signed in to change notification settings - Fork 126
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.9.0 #944
Labels
Comments
42 tasks
Merged
Performance Test Results 2.9ConfigurationsData Sets
Total Queries: 10,000 Cluster Configuration
Client Configuration
VisualizationsPerf Results Comparison Between 2.8.0 and 2.9.0Ingest took totalQuery took p50Query took p99Perf Results Comparison in 2.9.0Query took totalQuery took p50Query took p99Faiss filtersLucene filtersResultsnmslib-hnsw
faiss-hnsw
faiss-hnsw relaxed-filter
faiss-hnsw restrictive-filter
faiss-ivf
faiss-ivfpq
lucene-hnsw
lucene-hnsw restrictive-filter
lucene-hnsw relaxed-filter
|
K = 100 in all the above experiments. |
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a component issue for {REPLACE_WITH_RELEASE_VERSION}.
Coming from opensearch-project/opensearch-build#3616. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue
This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
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. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly. Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on
__{REPLACE_MAJOR_MINOR_PATCH}__
branch to__{REPLACE_MAJOR_MINOR_PATCH}__
for Min/Core, and__{REPLACE_MAJOR_MINOR_PATCH_0}__
for components. Otherwise, keep the version number unchanged for both.Preparation
v__REPLACE_MAJOR_MINOR_PATCH__
.CI/CD
__{REPLACE_MAJOR_MINOR_PATCH}__
are complete.Pre-Release
__REPLACE_MAJOR_MINOR__
release branch in the distribution manifest.__{REPLACE_MAJOR_MINOR_PATCH}__
have been merged.Release Testing
Release
Post Release
The text was updated successfully, but these errors were encountered: