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

• [ ] #30
• [X] #31
• via #48
• [x] #33
• Concensus: Minor version in sync (re-open if issue needs re-visiting)
• [X] #34
• via #43
• [x] #36
• [x] #38
• [x] #41
• re-directed #56
• [x] #44
• Consensus: due to lock-step with rustls we cannot control MSRV upgrades
• [ ] #49
• [ ] #50
• [ ] #52
• [ ] #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 :)

• https://github.com/RustCrypto/rustls-rustcrypto/issues/33