Release OpenSearch and OpenSearch Dashboards 1.3.9

I noticed that a manifest was automatically created in manifests/1.3.9. Please follow the following checklist to make a release.

Preparation

• Assign this issue to a release owner.
• Declare a pencils down date for new features to be merged.
• Mar 9, 2023 is pencils down date for feature freeze.
• Update the Campaigns section to include monitoring campaigns during this release.
• Update this issue so all __1.3.9__ placeholders have actual dates.
• Document any new quality requirements or changes.
• Finalize scope and feature set and update the Public Roadmap.
• Create a release issue in every component repo that links back to this issue, update Components section with these links.
• Ensure the label is created in each component repo for this new version, and the next minor release. Create a version label
• Ensure that all release issues created above are assigned to an owner in the component team.
• Increase the build frequency for the this release from once a day (H 1 * * *) to once every hour (H/60 * * * *) in jenkinsFile.

Campaigns

Code Complete - Ends Mar 9, 2023

• Code Complete: 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 version manifest.
• Verify pull requests to add each component to manifests/1.3.9/opensearch-1.3.9.yml and manifests/1.3.9/opensearch-dashboards-1.3.9.yml have been merged.
• Gather, review and combine the release notes from components repositories.

Release testing - Ends Mar 14, 2023

• Declare a release candidate build, and provide the instructions with the release candidates for teams on testing (Mar 10, 2023).
• Stop builds for this version of OpenSearch and/or OpenSearch Dashboards in order to avoid accidental commits going in unknowingly. Restart only if necessary else manually run the build workflow and declare new release candidate.
• After generate the release candidates, raise PR to lock input manifest refs of both OS and OSD builds with the commit ids from distribution manifest of the release candidates.
• Sanity Testing (Mar 10, 2023 - Mar 14, 2023): Sanity testing and fixing of critical issues found by teams. Teams test their components within the distribution, ensuring integration, backwards compatibility, and perf tests pass.
• Publish all test results in the comments of this issue.

Release - Mar 16, 2023

• Verify all issues labeled v1.3.9 in all projects have been resolved.
• Complete documentation for this release.
• Author blog post for this release.
• __Mar 16, 2023 - Publish this release on opensearch.org.
• __Mar 16, 2023 - Publish a blog post - release is launched!

Post Release

• Create release tags for each component (Jenkins job name: release-tag-creation).
• Replace refs in manifests/1.3.9 with tags and remove checks.
• If this is a major or minor version release, stop building previous patch version.
• Generate distribution release notes reviewed by PM team for opensearch-build repository.
• Increment version for Helm Charts (sample PR) for the 1.3.9 release.
• Increment version for Ansible Charts (sample PR) for the 1.3.9 release.
• Prepare for next patch release by incrementing patch versions for each component.
• Update this template with any new or missed steps.
• Create an issue for a retrospective, solicit feedback, and publish a summary.

Components

Replace with links to all component tracking issues.