[RELEASE] Release version 1.3.13

[github-actions]

Release OpenSearch and OpenSearch Dashboards 1.3.13

I noticed that a manifest was automatically created in manifests/1.3.13. 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

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

Release Branch and Version Increment

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

Feature Freeze - Ends Sep 14th

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

Code Complete - Ends Sep 14th

• Mark this as done once the Code Complete is reviewed.
• Create/Verify pull requests to add each component to relase input manifests/1.3.13/opensearch-1.3.13.yml and manifests/1.3.13/opensearch-dashboards-1.3.13.yml.

Release Candidate Creation and Testing - Ends Sep 15th

• Generate Release Candidate.

• Integ Test TAR.

• Integ Test RPM.

• Docker Build and Scan.

• Backwards Compatibility Tests.

• Windows Integration Test.

• Broadcast and Communication.

• Release Candidate Lock.

• Post the benchmark-tests

• Longevity tests do not show any issues.

Pre Release - Ends Sep 20th

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

Release - Ends Sep 21st

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

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

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

Legend

Symbol	Meaning
🟢	On track with overall release
🟡	Missed last milestone
🔴	Missed multiple milestones

[peterzhuamazon]

Pending Issues:

• Make sure 1.x is build on CentOS7 and AL2, with nodejs10 untouched on the pipelines