[Retrospective] Release version 1.3.2

[zelinh]

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.

[peternied]

Initially there were component issues for this release, then those were not used

[peternied]

The release issue was not getting much attention from individuals / teams, there were many preparation checklist items unchecked well into the 'coding' phase of the release.

[CEHENKLE]

I don't feel confident yet on the state of our automation. It seems like need two things before I'm (more) confident: 1) weekly inspection of code %/mechanism in place to block merges for commits that reduce coverage. 2) A review/some other confidence builder on the goodness of those tests. It's not enough to exist, they have to be comprehensive. 3) A review/some other confidence build on the existence/goodness of integration tests.

[CEHENKLE]

Setting latest to 2.0 RC1 and then setting latest to 1.3.2 caused customer pain and confusion opensearch-project/OpenSearch#3222 We're going to have the exact same problem when 3.0rc comes out in Sept -- can we either have major/minor tags or we don't set the 3.0 RC to latest.

[CEHENKLE]

Our performance tests missed an issue with performance #2054 Either we're not testing what we think we are (opensearch-project/OpenSearch#2985), or we are testing things but not inspecting/alerting on results

[bbarani]

We will be fixing opensearch-project/OpenSearch#3222 in #1621.

[bbarani]

Closing the 1.3.2 retro issue since its been 10 days post the release. Feel free to re-open if needed.