Add "Announcing Clippy feature freeze post

[blyxyas]

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:

• What's happening and when
• Why it's happening
  • Too many lints
  • More bugs that we'd like
• What can the users expect
  • Better lints, more accurate ones
  • No breaking changes
  • Faster development cycle
  • New lints will have to wait these 3 months
• How can you help
  • Every contribution helps
  • If you want direct help,

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

[llogiq]

Some small fixes. Good job on the blog post!

[flip1995]

I would not call it "the summer of Clippy", but rather by what it is: a feature freeze. All other comments are quite pedantic.

[blyxyas]

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

[samueltardieu]

@blyxyas Can you add the tracking issue link and merge this? The deadline is approaching, and a heads up to prevent contributors from starting work on new lints that won't be merged before 3 months would be useful (I just had to warn a new contributor today).

[blyxyas]

Done! @Manishearth or @flip1995 could you merge this (I'd do it myself but don't have the repo permissions)