-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Retrospective] Release 1.2.0 #880
Comments
Component tickets off of the 1.2.0 release issue don't have dates on them. It makes it hard to know what the critical dates are from a component. Originally this was by design to prevent dates from drifting away from the agreed central data source of the primary release ticket. Possible solutions:
|
Checkstyle removed from OpenSearch opensearch-project/OpenSearch#1370, that caused AD plugin 1.2 build failed, took team hours to figure out why. We should notify all plugin teams about such changes in future. |
Automate snapshot builds were being created and used by the distribution downloader tool and they were out of date #953. A few issues this exposed:
|
Seeing random test failures, might be associated with out of data code that was copypasted |
Random integration test failures seem to happen frequently, the starting point of a test failure investigation is 'is this a random failure' indication low trust in the test systems. |
There was some confusion of what should and what should not be included in the manifest, see #974. |
|
For improvement, plugin version bumping and adding to manifest as soon as possible would be ideal. Logically once a |
Reflecting on OpenSearch Release 1.2.0, 1.2.1, 1.2.2, and 1.2.3.There have been a massive number of contributors authoring code, reviewing pull requests, contribution to issues – thank you all. Larger areas of consideration
Action Items
With this we are closing out the retro items for 1.2.0-1.2.3 - its 2022 🎆 and I can not wait for the next set of releases! |
The OpenSearch and OpenSearch Dashboards Release 1.2.0 is currently in progress. To make sure that we do not lose issues that arose during the process please add them here. This issue will be updated after the release is finished.
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.
The text was updated successfully, but these errors were encountered: