0.23 release preparation

[cpu]

Let's collect up a burndown list of tasks to be completed for a 0.23 release that includes FIPS support and the new choice for default crypto provider.

• Next steps for Quinn support (cont'd) #1798
• server: allow acceptor to send alerts after error #1811
• [3/3] no-std support phase I #1502 (maybe)
• Avoid unnecessary allocation and copy in OpaqueMessage::encode #1774
• Limit fragmentation in write_vectored #1640
• Correct kx group selection #1784
• Improve provider and FIPS documentation #1789
• Change crate default features to use aws-lc-rs #1780

[cpu]

I've proposed a handful of items to consider blocking on.

I think #1640 is very close and probably uncontroversial. I'm not sure if we want to roll #1774 in as well.

It feels important to tie a bow on the outstanding changes Quinn needs in #1741.

I think we're missing an issue to link for switching the default provider.

[djc]

This list looks good to me!

[cpu]

Added #1784 & #1789 to the list.

[cpu]

Thinking about #1502 and 0.23 - I don't think it's a must-have, but it might also not be something we could turn around in a 0.23.1.

I think (writing this out in case I'm wrong) adding the std feature and putting it in the default features list is a breaking change because there are folks that could be using rustls with default-features = false who would now need to add std to the features they enable, or suffer breakage from API surface disappearing.

[ctz]

Yes, unfortunately I think any change to the default feature list is a breaking change :(

[cpu]

Thanks for confirming. I put it in the list as a nice-to-have. Looking forward I think pt2 could be landed without breaking changes so it would be ideal if we could fit pt1 into this release, but if it doesn't happen it would be OK knowing there's further work to be done in either case.

[djc]

Would be nice to get #1811 in.

[cpu]

Would be nice to get #1811 in.

Added to the list. It's in the merge queue now.

[cpu]

v0.23.0 was published this morning 🚀