-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[stable14] always query the lookup server in a global scale setup #11800
Conversation
…er label Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Don't worry I always go through all the "backport-request" PRs upon the arrival of a new maintenance release. It's just a mess to keep two branches in sync just for the reminder. THat's the reason I closed the other one. We do this way with so many PRs. So we are quite skilled to handle it this way. 😉 But because it is you I will keep it open. But for the next time you know that we will not forget to backport your PR. 🎉 |
Don't worry, I will take care of it. 🙂 As long as it is labeled as "in development" it is also not a problem if it is not always 100% in sync. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
backport of #11714
I added the "developing" label as a indicator that you can ignore it until the master pr is merged. But please keep it open. So that in the unlikely case that this will not be merged before we are approaching 14.0.4 we have the PR with the milestone as a reminder that there is something which should be part of the release.