Release 0.23.0 Tracker

[pinkforest]

What should we add to the initial release ?

TL;DR "it's tested sane" a.k.a "it builds, it tests, it benches, it's no_std, it's crypto is sane" ?

Release 0.23.0 train

• Add / ensure IETF TLS 1.3 test vectors covered #30
• Self-test / map between rustls / CryptoProvider Validaton / Tests #31
• via Add rustls builder integration tests #48
• rustls Sync / Integration Lock-Step #33
• Concensus: Minor version in sync (re-open if issue needs re-visiting)
• Feature downstream dependency mapping #34
• via Use dependencies default-features = false where possible #43
• no_std gating - gate-in alloc #36
• Support & build test no_std/alloc #38
• API for providing Rng #41
• re-directed Document no_std with getrandom #56
• MSRV Policy & Control #44
• Consensus: due to lock-step with rustls we cannot control MSRV upgrades
• Integration tests - Internal localhost #49
• Benchmarks #50
• Algo tester #52
• 0.23.0 Documentation #53 (all doc issues wrapped into this)

need to raise some more issues me thinks

[tarcieri]

I think it might make sense to match version numbers with rustls to make compatibility more obvious

[pinkforest]

So first release would be 0.23.0 ?

• What happens if/when we have (we already have provider() constructor) our own API and we need to bump our API ?
• And what happens when we need to bump MSRV - can we do this at patch level 0.23.X bumps ?

Started an issue for it :)

• rustls Sync / Integration Lock-Step #33