Release version 1.3

[zelinh]

This is a component issue for release 1.3.0.

Coming from opensearch-build#889, release version 1.3. Please follow the following checklist.

Preparation

• Assign this issue to a release owner.
• Finalize scope and feature set and update the Public Roadmap.
• Create, update, triage and label all features and issues targeted for this release with v1.3.0.

CI/CD

• Increment version on main to 1.3.0.0 1.4.0.0
• Ensure working and passing CI.
• Re(add) this repo to the (if not exist) manifest.

Pre-Release

• Branch and build from a 1.3 branch.
• Update your branch in the manifest.
• Feature complete, pencils down.
• Fix bugs that target this release.

Release

• Complete documentation.
• Gather, review and publish release notes.
• Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

• Create a release tag.
• Suggest improvements to this template.
• Conduct a postmortem, and publish its results.

[dreamer-89]

Branch 1.3 created.
https://github.com/opensearch-project/OpenSearch/compare/1.x...1.3?expand=1

[dreamer-89]

Need to update BWC versions & builds post bumping 1.x moved to 1.4.

#2430

[dreamer-89]

To generate release notes, used below command

git checkout 1.x (# ensure your 1.x is upto date)
git-release-notes ce7b091da6ae50bbc3c015a78b7611923475386c..a61080d9d027a970784825f8486f686a63aa951c markdown > /tmp/1.3_release_notes. (commits identified from previous releases commit messages)

[dreamer-89]

Opened issue on opensearch-website for documentation side changes.
opensearch-project/documentation-website#448

[dreamer-89]

Based on my first release manager experience, sharing below points for improvement.

Generic

• There should be some rough timelines on when specific task needs to be started (and completed if other process is dependent on it).

Preparation

• Triaging and labeling issues for release should be done on recurring basis. Doing this as one time activity before release is error prone.

CI/CD

• Add step for incrementing the main next release version. Added here: Fixing bwcVersions and bwc builds #2430
• Add step for incrementing the next patch version. Added here: Bump the version to 1.3.1 #2509
• Re(add) this repo to the (if not exist) [manifest](https://github.com/opensearch-project/opensearch-build/blob/main/manifests/1.3.0/). This step is not applicable for OpenSearch engine as it being core repository.

Release

• As mentioned here, we can make use of tools like git-release-notes to get release notes in markdown.
• Remove the dependabot commits (feedback from @dblock @stockholmux ) from generated release notes.

Post Release

• Create a release tag can be removed as there is already automation in place to create those automatically.

[dreamer-89]

Following up with @elfisher on documentation task, before closing on this one.

[dreamer-89]

Release retro issue opensearch-project/opensearch-build#1775

[dreamer-89]

Still waiting for closure on documentation issue before closing this one.