[Retrospective] Release version 2.7.0

[zelinh]

#3230

How to use this issue?
Please add comments to this issue, they can be small or large in scope. Honest feedback is important to improve our processes, suggestions are also welcomed but not required.

What will happen to this issue post release?
There will be a discussion(s) about how the release went and how the next release can be improved. Then this ticket will be updated with the notes of that discussion along side action items.

[bbarani]

These are the PRs that were causing the delay of 2.7.0 release.

OpenSearch Dashboards:
opensearch-project/OpenSearch-Dashboards#3920
opensearch-project/OpenSearch-Dashboards#3922
opensearch-project/dashboards-observability#416
opensearch-project/OpenSearch-Dashboards#3912
opensearch-project/dashboards-observability#406

OpenSearch:
opensearch-project/security-analytics-dashboards-plugin#551
opensearch-project/security-analytics-dashboards-plugin#550
opensearch-project/OpenSearch#7292
opensearch-project/OpenSearch#7297

Documentation:
opensearch-project/documentation-website#3741
opensearch-project/documentation-website#3814
opensearch-project/documentation-website#3803
opensearch-project/documentation-website#3443
opensearch-project/documentation-website#3815

[bbarani]

Discovered last minute CVE-2022-45688

[vagimeli]

Documentation team/technical writers must have the features' testing sites that mimic the users' experience as early as possible, not at code freeze. For 2.7 release, the dev sites weren't sufficient for creating visuals, as the UI differed from the released version. The writers then have to backtrack to update the newly released documentation. Suggestion: When a doc issue is created, devs include the testing site or an update on the testing site status.

[bbarani]

Closing this issue as we have released 2.7.0 version.