release_template.md

name	title	labels
Release	[RELEASE] Release version {{ env.VERSION }}	untriaged, release, v{{ env.VERSION }}

Release OpenSearch and OpenSearch Dashboards {{ env.VERSION }}

I noticed that a manifest was automatically created in [manifests/{{ env.VERSION }}](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}). 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 (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.

Preparation

• Release manager assigned.
• Existence of label in each component repo. For more information check the release-label section.
• Increase the build frequency.
• Release Issue.

Campaigns

• Components Release Issue.
• Release Campaigns.

Release Branch and Version Increment - _Ends REPLACE_RELEASE-minus-14-days

• Core Release Branch.
• Core Version Increment.
• Components Release Branch.
• Components Version Increment.

Feature Freeze - _Ends REPLACE_RELEASE-minus-12-days

• OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.

Code Complete - Ends REPLACE_RELEASE-minus-10-days

• 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 input manifest.
• Create/Verify pull requests to add each component to relase input [manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-{{ env.VERSION }}.yml) and [manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml](/opensearch-project/opensearch-build/tree/main/manifests/{{ env.VERSION }}/opensearch-dashboards-{{ env.VERSION }}.yml).

Release Candidate Creation and Testing - Ends REPLACE_RELEASE-minus-6-days

• Generate Release Candidate.
• Integ Test TAR.
• Integ Test RPM.
• Docker Build and Scan.
• Backwards Compatibility Tests.
• Windows Integ Test.
• Broadcast and Communication.
• Release Candidate Lock.

Performance testing validation - Ends REPLACE_RELEASE-minus-6-days

• Performance tests do not show a regression.
• Longevity tests do not show any issues.

Pre Release - Ends REPLACE_RELEASE-minus-1-days

• Release Labeled Issues.
• Go or No-Go.
• Promote Repos.
• Promote artifacts.
• Release Notes.

Release - _Ends {_REPLACE_RELEASE-day}

• Maven Promotion.
• Docker Promotion.
• Release Validation.
• Collaboration with the Project Management Team.

Post Release

• Release Tags.
• Input Manifest Update.
• OpenSearch Build Release notes.
• Decrease the build frequency.
• Retrospective Issue.
• Helm and Ansible Playbook release.

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