Skip to content

Latest commit

 

History

History
159 lines (120 loc) · 10.4 KB

release_template.md

File metadata and controls

159 lines (120 loc) · 10.4 KB
Raw
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.

Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.

Preparation

Campaigns

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

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

  • Mark this as done once the Code Complete is reviewed.
  • 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

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

  • Post the benchmark-tests
  • Longevity tests do not show any issues.

Pre Release - Ends REPLACE_RELEASE-minus-1-days

Release - _Ends {_REPLACE_RELEASE-day}

Release Checklist.


Release Checklist

Pre-Release activities

  • Promote Repos.
      • OS
      • OSD
  • Promote Artifacts.
      • Windows
      • Linux Debian
      • Linux RPM
      • Linux TAR
  • Consolidated Release Notes.

Release activities

  • Docker Promotion.
  • Release Validation part 1.
      • OpenSearch and OpenSearch Dashboard Validation.
      • Validate the native plugin installation.
  • Merge consolidated release notes PR.
  • Website and Documentation Changes.
      • Merge staging website PR.
      • Promote the website changes to prod.
      • Add website alert.
  • Release Validation part 2.
      • Validate the artifact download URL's and signatures.
  • Release Validation part 3.
      • Trigger the validation build (Search for Completed validation for <> in the logs).
  • Maven Promotion.
  • Publish blog posts.
  • Advertise on Social Media.
  • Post on public slack and Github Release issue.

Post-Release activities

  • Release Tags.
  • Input Manifest Update.
  • Decrease the Build Frequency.
  • OpenSearch Build Release notes.
  • Retrospective Issue.
  • Helm and Ansible Playbook release.
  • Upcoming Release Preparation.


Post 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