Skip to content
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 Version 2.14.0 #4712

Closed
rishabh6788 opened this issue May 15, 2024 · 2 comments
Closed

[Retrospective] Release Version 2.14.0 #4712

rishabh6788 opened this issue May 15, 2024 · 2 comments

Comments

@rishabh6788
Copy link
Collaborator

Related release issue?

#4562

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.

@github-actions github-actions bot added the untriaged Issues that have not yet been triaged label May 15, 2024
@sandervandegeijn
Copy link

Some points that come to mind (no offense intended of course!):

The project roadmap is lagging behind somewhat: https://github.com/orgs/opensearch-project/projects/1 - 2.14 has been released and the contents there isn't matching what's been released in 2.14. 2.15 is not on there, 3.0.0 isn't scheduled yet. Clarification would help.

@ananzh was investigating a lot of dashboards issues that seemed to be on the radar for 2.14: opensearch-project/OpenSearch-Dashboards#6292 Would be nice if 2.15.0 contains fixes for these kinds of issues, a lot of them seem relatively simple but can be annoying for the end user.

Personally I was a tad disappointed that opensearch-project/OpenSearch#11676 hasn't been fixed while it's breaking released functionality since 2.11. Although I do understand the invitation to help out in terms of code, this is not something that's viable for everyone. It would be nice if bugs that are this severe would take priority over optimizing performance (which is already really really good!).

@gaiksaya
Copy link
Member

Adding @bbarani @Pallavi-AWS to this conversation.

@gaiksaya gaiksaya removed the untriaged Issues that have not yet been triaged label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants