-
Notifications
You must be signed in to change notification settings - Fork 13.3k
beta backport PR 52232 #52311
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
Comments
@rfcbot fcp merge I propose that we approve backporting #52232 to beta. Since time is somewhat limited, and back ports are usually less controversial than the usual things that go through the fcp process, I'm going to add the additional note: if there are no unresolved formal concerns in a week's time, I will just check off any unmarked check boxes. (This effectively inverts the rfcbot into "approved by default.") |
Team member @pnkfelix has proposed to merge this. The next step is review by the rest of the tagged teams:
No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
What about stable? |
ugh I guess I will open a separate issue for stable? hashtag what a pain |
(who was the genius who suggested using async to resolve this. ... ;) |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
This is a dummy issue linking to PR #52232 so that we can have an open issue (which is apparently a requirement if one wants to leverage the rfcbot).
The text was updated successfully, but these errors were encountered: