Release 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.
• 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]

Note; only outstanding change currently in this repo is #83 which looks specific for notifications. I'll operate as the defacto owner until we can get someone better suited @lezzago will be covering this release.

[peternied]

@lezzago Are there any additional issues/PRs that need to have the v1.2.0 tag applied? If not, then you can close out all the preparation tasks.

[lezzago]

@peternied There are no more PRs that need v1.2.0 tag on them. I have closed out all the preparation tasks.

[dblock]

I see a lot of issues in https://github.com/opensearch-project/common-utils/issues that are untriaged.

[peternied]

@lezzago 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?

[lezzago]

@peternied, I am not able to mark the test as completed in the issue, can you please do it for me? The tests did not have any issues.

[dblock]

1.2 has shipped a long time ago, closing