Tracking issue for v0.2.0 release

[tarcieri]

This is a tracking issue for a v0.2.0 release which represents a blocker for the next series of trait crate releases: RustCrypto/traits#1571

There are no specific release blockers I am aware of. I have only held off until we are ready to start releasing trait crates just in case something else pops up which might require a breaking change.

[tarcieri]

One thing we should check before a release is that we've properly deprecated all of the old GenericArray methods we don't intend to support going forward

Edit: this should be done now

[tarcieri]

Remaining things to do:

• Refactor extra-sizes into smaller features that can be switched on individually
• Switch to core::error::Error
• Remove std feature

[Christiaan676]

@tarcieri Can you explain what you want for the refactoring of extra-sizes?

One thing I can think of is creating the features: ML-DSA-sizes, SLH-DSA-sizes and ML-KEM-sizes. Along with the extra-sizes for the 1040-4080 sizes.

[tarcieri]

I removed it from the list. I was thinking about trying to decompose the feature into more granular ones that could be flipped on individually, but that really only helps for large blocks of values which we don't really have a need for (yet).

[tarcieri]

I'd say we're good to go now, though I'd like to hold off until Rust 1.82 is out before cutting a final release after merging #85.

That's scheduled for October 17th.

[jmwample]

Is there any chance of a v0.2.0-rc.10 release before 1.82 is released next month?

[tarcieri]

Sure!