0.20.0 release planning

[djc]

I think we're in a pretty good shape at this point. Work remaining:

• Change Connection to be an enum instead of a trait #789 is a pretty impactful public API change
• Fixes for TLS 1.2 session resumption #799 fixes the session resumption issues from Session resumption in TLS 1.2 violates RFC  #797
• Add Acceptor API for resolving server configuration based on ClientHello #787 has a minor public API change, and solves a somewhat popular issue

Unfortunately work on tokio-rustls appears to be stalled for now. The tokio-rustls implementation of the Acceptor API works for a little while but then starts timing out. That seems unlikely to be an issue in rustls, though (for now there is no local reproduction path).

[djc]

I suppose we should also consider #803 before the release. The recommendations made there make sense to me.

[djc]

Everything has been merged here. Follow-up question about the changes from #819:

Should we make CT off by default (no need to call without_certificate_transparency_logs()), enabled by calling the builder method explicitly in one of the later stages? (That is, leave it disabled implicitly?)

[djc]

Solved that in #826. @ctz do you want to do another beta or shall we kick this thing out already?

[djc]

(I can also take care of releasing it if you prefer, let me know if there are any steps I should be sure not to miss.)

[ctz]

https://crates.io/crates/rustls/0.20.0

(I can also take care of releasing it if you prefer, let me know if there are any steps I should be sure not to miss.)

For the future I've written these down on https://github.com/rustls/rustls/blob/main/RELEASING.md

[djc]

Thanks!