-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Stabilize transpose_result
in 1.33
#57567
Conversation
✌️ @alexreg can now approve this pull request |
This comment has been minimized.
This comment has been minimized.
1dad774
to
338d238
Compare
@bors r+ |
📌 Commit 338d238e79d2e38f15adf5b2b034d54bf53e72ce has been approved by |
This comment has been minimized.
This comment has been minimized.
338d238
to
6d7a4a6
Compare
@bors r=alexreg |
📌 Commit 6d7a4a6 has been approved by |
Stabilize `transpose_result` in 1.33 fixes #47338. FCP completed: #47338 (comment) r? @alexreg
☀️ Test successful - checks-travis, status-appveyor |
Was the discussion in the tracking issue taken into account when stabilising? There was discrepancy on the name that wasn't resolved. |
@clarcharr I read the discussion but was personally not convinced that it should stop stabilization; however, I'm not on the libs team. The FCP completed, so no one in the libs team found the bikeshed sufficiently important to raise a concern. If you think it's important enough, talk to a libs member and convince them to backport a name change to beta. |
fixes #47338.
FCP completed: #47338 (comment)
r? @alexreg