Update breaking changes template to incorporate ES deprecations #100621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the
8.0 Breaking changes
issue template to incorporate ES deprecations.Background:
We'd like to streamline the process for gaining awareness of any Elasticsearch-specific deprecations that may need support in Upgrade Assistant. My hope is that we can direct ES engineers to open issues using this template when additional work in UA is needed.
How to review:
Looking for feedback as to if it's confusing combining Kibana and Elasticsearch deprecations in the same template, and if it would be clearer if we had two separate issue templates. Also, anything else you think would be helpful to include here.