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.

Sign up for GitHub

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

Jump to bottom

Libs team meetings: Track regressions and critical issues #15

Open
m-ou-se opened this issue Jun 15, 2021 · 0 comments
Open

Libs team meetings: Track regressions and critical issues #15

m-ou-se opened this issue Jun 15, 2021 · 0 comments
Labels
meta Discussion about Libs itself

Comments

@m-ou-se
Copy link
Member

m-ou-se commented Jun 15, 2021 •
edited
Loading

In our libs meetings, we should make sure to track and respond to issues tagged as high/critical priority, or as regressions, such as rust-lang/rust#85667 and rust-lang/rust#85694. For the T-libs label, nobody is doing this right now. For the T-libs-impl label, the compiler team handles this right now, but we should take that over, in our new (non-api) meetings.

(We should probably change the first label to T-libs-api too.)
@m-ou-se m-ou-se added the meta Discussion about Libs itself label Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta Discussion about Libs itself
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@m-ou-se