Release OpenSearch 3.3.1
I noticed that a manifest was automatically created in manifests/3.3.1. Please follow the following checklist to make a release.
This release is opened due to a bug in the original 3.3.0 release, only OS updated to 3.3.1 version here.
Related PRs:
Release Schedule:
- 2025/10/17: OpenSearch Core issues resolve by EOD Friday
- 2025/10/17: First RC build by late Friday and run integTest of all OS 3.3.1 + OSD 3.3.0
- 2025/10/20: Evaluate with Core owner & sanity test
2025/10/21: Quick release 3.3.1 launch on Tuesday
- 2025/10/22: Quick release 3.3.1 launch on Wednesday due to a small bug
Potential 3.3.2 2025/10/30 (Pending Backport 3.3) ⚠️
- opensearch-build:
- OpenSearch:
- Docs:
- Potential Neural Search
- Potential ML/MCP:
- Potential k-NN:
- Potential skills:
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee (Release Manager) 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. For more information check the the Release Process OpenSearch Guide.
Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.
Release Checklist
| Criteria |
Status |
Description |
Comments |
| Each component release issue has an assigned owner |
🔴 |
|
|
| Documentation draft PRs are up and in tech review for all component changes |
🔴 |
|
|
| Sanity testing is done for all components |
🔴 |
|
|
| Code coverage has not decreased (all new code has tests) |
🔴 |
|
|
| Release notes are ready and available for all components |
🔴 |
|
|
| Roadmap is up-to-date (information is available to create release highlights) |
🔴 |
|
|
| Release ticket is cut, and there's a forum post announcing the start of the window |
🔴 |
|
|
| Any necessary security reviews are complete |
🔴 |
|
|
| Criteria |
Status |
Description |
Comments |
| Performance tests are run, results are posted to the release ticket and there no unexpected regressions |
🔴 |
|
|
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days |
🔴 |
|
|
| Documentation has been fully reviewed and signed off by the documentation community. |
🔴 |
|
|
| All integration tests are passing |
🔴 |
|
|
| Release blog is ready |
🔴 |
|
|
OpenSearch-Dashboards 3.3.1 exit criteria status:
| Criteria |
Status |
Description |
Comments |
| Documentation has been fully reviewed and signed off by the documentation community |
🔴 |
|
|
| No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days |
🔴 |
|
|
| All integration tests are passing |
🔴 |
|
|
| Release blog is ready |
🔴 |
|
|
Version Increment - _Ends REPLACE_RELEASE-minus-10-days
Feature Freeze - _Ends REPLACE_RELEASE-minus-12-days
Code Complete - Ends REPLACE_RELEASE-minus-10-days
Pre Release - Ends REPLACE_RELEASE-minus-1-days
Release - _Ends {_REPLACE_RELEASE-day}
Pre-Release activities
Release activities
Components
Replace with links to all component tracking issues.
| Component |
On track |
Release Notes |
| {COMPONENT_ISSUE_LINK} |
{INDICATOR} |
{STATUS} |
Legend
| Symbol |
Meaning |
| 🟢 |
On track with overall release |
| 🟡 |
Missed last milestone |
| 🔴 |
Missed multiple milestones |
Release OpenSearch 3.3.1
I noticed that a manifest was automatically created in manifests/3.3.1. Please follow the following checklist to make a release.
This release is opened due to a bug in the original 3.3.0 release, only OS updated to 3.3.1 version here.
Related PRs:
Release Schedule:
2025/10/21: Quick release 3.3.1 launch on TuesdayPotential 3.3.2 2025/10/30 (Pending Backport 3.3)⚠️
How to use this issue
This Release Issue
This issue captures the state of the OpenSearch release, its assignee (Release Manager) 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. For more information check the the Release Process OpenSearch Guide.
Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.
Release Checklist
Entrance Criteria
OpenSearch 3.3.1 exit criteria status:
OpenSearch-Dashboards 3.3.1 exit criteria status:
Preparation
Campaigns
Version Increment - _Ends REPLACE_RELEASE-minus-10-days
Feature Freeze - _Ends REPLACE_RELEASE-minus-12-days
Code Complete - Ends REPLACE_RELEASE-minus-10-days
Release Branch, Release Candidate Creation and Testing - Ends REPLACE_RELEASE-minus-6-days
Performance testing validation - Ends REPLACE_RELEASE-minus-6-days
Pre Release - Ends REPLACE_RELEASE-minus-1-days
Release - _Ends {_REPLACE_RELEASE-day}
Release Checklist.
Pre-Release activities
Release activities
Completed validation for <>in the logs).Post Release
Components
Replace with links to all component tracking issues.
Legend