Release version 1.2

[dblock]

Coming from opensearch-build#567, release version 1.2. 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.2.0.

CI/CD

• Increment version on main to 1.2.0.0. (Pull Updates performance analyzer version to 1.2 #71 )
• Ensure working and passing CI.
• Re(add) this repo to the manifest.

Pre-Release

• Branch and build from a 1.2 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.

[peternied]

@opensearch-project/performance-analyzer Could we assign someone to this issue to drive the 1.2 release?

[peternied]

@opensearch-project/performance-analyzer Could we update this ticket to reflect who is assigned to the 1.2 release?

[peternied]

@kjoseph07 @sruti1312 Could you update this ticket with the current status by EOD? From the master ticket, today all components should be done with preparation tasks and be in development for 1.2.0 features.

[peternied]

There is a bundle build break from PA, see opensearch-project/opensearch-build#885

[peternied]

@sruti1312 @kjoseph07 Until Friday the 12th at noon PST, any tests that use distribution downloader were running against old bits and need to be rerun. Can you please see if your team was impacted, rerun the tests, and then mark the tests run as completed in opensearch-project/opensearch-build#954?

[peternied]

@peterzhuamazon found an issue that looks like it was suppose to be resolved in the v1.2.0 release, please investigate #82

[peterzhuamazon]

@peterzhuamazon found an issue that looks like it was suppose to be resolved in the v1.2.0 release, please investigate #82

Just talked with @sruti1312 and the confusion is cleared up
We dont need to include RCA in manifest as the gradle build action in PA repo will auto checkout RCA and both will be built and bundled into one ZIP.
@sruti1312 will send a PR to remove RCA from the input manifest.
Thanks.

[kjoseph07]

The release tags have been published. Any postmortem (retrospective) issues will be added to this retrospective issue.