[RELEASE] Release version 1.3.8

[tianleh]

This is a component issue for 1.3.8.
Coming from opensearch-build#3012. Please follow the following checklist.
Please refer to the DATES in that post.

How to use this issue

This Component Release Issue

This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visibility into the release status.

Release Steps

There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.

Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.

The Overall Release Issue

Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly. Please contact them or @mention them on that issue for help.

What should I do if my plugin isn't making any changes?

If including changes in this release, increment the version on 1.x branch to 1.3.8 for Min/Core, and 1.3.8.0 for components. Otherwise, keep the version number unchanged for both.

Preparation [Done]

• Assign this issue to a release owner
• All the tasks in this issue have been reviewed by the release owner.
• Create, update, triage and label all features and issues targeted for this release with v1.3.8.
• All code changes for 1.3.8 are complete.
• Create branch 1.3

Pre-Release

• Update to the 1.3 release branch in the distribution manifest.
• Increment the version on the parent branch (1.x) to the next development iteration (1.3)
• Confirm that all changes for 1.3.8 have been merged.

During Release Testing

• Review any PRs in this repo during the release

Release

• Complete [documentation] if there's any changes (https://github.com/opensearch-project/documentation-website).
• Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

• Add this repo to the manifest for the next developer iteration. (1.3.9)
• Add this repo to the manifest of the next eventual security patch version. (1.3.9)
• Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
• Suggest improvements to this template.
• Conduct a retrospective, and publish its results.

[ananzh]

From what I checked last week, there is no issue/PR tagged v1.3.8.
I will pass this down for next on-call follow-up.

[ananzh]

@tianleh @CCongWang Is this 1.3.8?

#424

Should tag it v1.3.8? Since this repo doesn't have the release note, is there a painless way to know which PR is not merged in for the previous release?

[tianleh]

From what I checked last week, there is no issue/PR tagged v1.3.8.
I will pass this down for next on-call follow-up.

Thanks! When there is no issue/PR tagged v1.3.8, the release work is as minimum as updating version in package.json during release.

[tianleh]

@tianleh @CCongWang Is this 1.3.8?

#424

Should tag it v1.3.8? Since this repo doesn't have the release note, is there a painless way to know which PR is not merged in for the previous release?

Yes. It has been backported to 1.3.

We shall tag the PR/issues by following this to make it easy to manage.
https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/main/RELEASING.md#release-labels I will remind PR reviewers/authors about this. Thanks!