Release 0.660 planning

[msullivan]

I'd like to release mypy 0.660 on Friday, January 11. I plan to cut the release branch on Monday, January 7.

I plan to also release our first official mypy_mypyc binary alongside it.

If there are any PRs that need to make it in for the release, please mention them here.

[Michael0x2a]

I have a host of Literal-types related PRs I'd like to get in if possible:

• Add intelligent indexing of tuples, NamedTuples, and TypedDict.

• Add tests for Literal types with incremental and fine-grained mode.

• Add interactions between Literal and Final.

I also have two lower-priority PRs I'd like to get merged in: the first is cosmetic, and the second is just documentation and doesn't necessarily need to make the cutoff.

• Improve error messages related to literal types.
• Add docs for literal types.

[JukkaL]

If we ship a compiled binary by default, maybe the version should be incremented to 0.700. This is a major change, even if it doesn't bring any new functionality.

I might also want to make --fast-exit enabled by default.

[msullivan]

I hadn't been planning to make the compiled binary the default in this release yet, just to release and publicize an alternate compiled package.

[emmatyping]

I would like to get #6148 in if possible. This should bring the daemon on Windows to feature parity with Unix.

[emmatyping]

It would also be nice to get #6153 in since it fixes a rather confusing crash with the daemon.

[JukkaL]

I hadn't been planning to make the compiled binary the default in this release yet, just to release and publicize an alternate compiled package.

Ok, 0.660 is good then and we don't need any --fast-exit changes.

[msullivan]

I am postponing the release to Wednesday, Jan 16. I'll cut the release branch later this week.

[Michael0x2a]

I have one final Literal-related PR I'd like to get in if possible. It should be a short one though: #6176

[msullivan]

I've cut the release branch

[msullivan]

We realized that it was a mistake to release typed_ast 1.1.1 with a breaking API change. As a result we are going to release a 1.2.0 and pull version 1.1.1, which means we need to get that out and update our dependency in mypy for this release.