-
Notifications
You must be signed in to change notification settings - Fork 303
Add "Announcing Clippy feature freeze post #1613
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
base: master
Are you sure you want to change the base?
Conversation
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.
Some small fixes. Good job on the blog post!
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.
I would not call it "the summer of Clippy", but rather by what it is: a feature freeze. All other comments are quite pedantic.
Closing and reopening this to avoid the automerge. We still need to address that tracking issue link missing. If closing and reopening doesn't pause the merge queue, I guess we can still fix this after the merge in a bugfix PR |
This is the initial draft for "The incoming Summer of Clippy", talked about in our All Hands.
For reviewing ease, here's everything I wanted to talk about:
We are currently blocked on not having a tracking issue for the good first issues (and we do not have a lot of issues marked with the label in the repo). But I think that this is still ready for an initial review from the team.
Related to https://hackmd.io/nubu1rGOTliW1MZPilplaA
@rust-lang/clippy
Rendered