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

[META] Track plugin backports refactoring XContent from common to core namespace #6841

Closed
1 of 25 tasks
nknize opened this issue Mar 27, 2023 · 6 comments
Closed
1 of 25 tasks
Labels
>breaking Identifies a breaking change. Meta Meta issue, not directly linked to a PR release v2.7.0

Comments

@nknize
Copy link
Collaborator

nknize commented Mar 27, 2023

From #6470 the following issues track backporting XContent refactor from common to core namespace on all affected downstream plugins:

Going forward this will not be a common practice of the core repo as downstream projects should not stall progress PRs for weeks on end.

@nknize nknize added Meta Meta issue, not directly linked to a PR >breaking Identifies a breaking change. labels Mar 27, 2023
@nknize nknize removed the untriaged label Mar 27, 2023
@nknize
Copy link
Collaborator Author

nknize commented Mar 27, 2023

Affected plugin repos have been assigned the v2.7.0 label for the next 2.x release.

@nknize
Copy link
Collaborator Author

nknize commented Mar 28, 2023

All issues have been updated w/ notice of merge

@DarshitChanpura
Copy link
Member

@nknize Since Apr 17, Monday will be code-free for v2.7.0 and there are still 4 issues pending for this META, what should be the next steps for this issue?

@nknize
Copy link
Collaborator Author

nknize commented Apr 14, 2023

@nknize Since Apr 17, Monday will be code-free for v2.7.0 and there are still 4 issues pending for this META, what should be the next steps for this issue?

I pinged the remaining issues to see if anything needs to be done. If no response then we move forward on the build.

@Rishikesh1159
Copy link
Member

No Response from the 4 issues pending for this META. Moving forward with build. @nknize can we close this issue?

@mch2
Copy link
Member

mch2 commented May 9, 2023

No response, closing.

@mch2 mch2 closed this as completed May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>breaking Identifies a breaking change. Meta Meta issue, not directly linked to a PR release v2.7.0
Projects
None yet
Development

No branches or pull requests

4 participants