-
Notifications
You must be signed in to change notification settings - Fork 278
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
[META] Planned Breaking Changes for 3.0 in Core/Plugins #5243
Labels
release
Roadmap:Releases/Project Health
Project-wide roadmap label
untriaged
Issues that have not yet been triaged
v3.0.0
Comments
peterzhuamazon
added
release
Roadmap:Releases/Project Health
Project-wide roadmap label
v3.0.0
labels
Jan 15, 2025
github-project-automation
bot
moved this to Backlog
in OpenSearch Engineering Effectiveness
Jan 15, 2025
peterzhuamazon
moved this from Backlog
to In Progress
in OpenSearch Engineering Effectiveness
Jan 15, 2025
peterzhuamazon
moved this from 🆕 New
to 🏗 In progress
in Engineering Effectiveness Board
Jan 15, 2025
peterzhuamazon
changed the title
[META] Planned Breaking Changes for 3.0 for Plugins
[META] Planned Breaking Changes for 3.0 for Core/Plugins
Jan 15, 2025
peterzhuamazon
changed the title
[META] Planned Breaking Changes for 3.0 for Core/Plugins
[META] Planned Breaking Changes for 3.0 in Core/Plugins
Jan 15, 2025
This was referenced Jan 16, 2025
Open
This was referenced Jan 16, 2025
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
opensearch-project/performance-analyzer#777
Open
Open
Open
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
opensearch-project/dashboards-reporting#487
Open
Open
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
opensearch-project/dashboards-assistant#391
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
release
Roadmap:Releases/Project Health
Project-wide roadmap label
untriaged
Issues that have not yet been triaged
v3.0.0
Is your feature request related to a problem? Please describe
This issue is being used to track and increase transparency around the breaking changes planned for the 3.0 release. The goal is to help the community get a preview of the breaking changes ahead of time so that migration details can be accounted for. Feedback on the process is welcomed.
Describe the solution you'd like
Each repo who plans to release breaking changes in 3.0 will have a sub-issue linked to this issue. This issue will be posted on the public roadmap for the community to see and provide feedback on. Contributors will do their best to highlight breaking changes early on in the process. Community members are encouraged to add feedback to the proposed breaking changes to improve the product offering.
Describe alternatives you've considered
We will be testing this process out and will learn as we go.
OS Plugins:
OSD Plugins:
Thanks.
The text was updated successfully, but these errors were encountered: