-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for v0.2.0 release #74
Comments
One thing we should check before a release is that we've properly deprecated all of the old Edit: this should be done now |
Remaining things to do:
|
@tarcieri Can you explain what you want for the refactoring of One thing I can think of is creating the features: |
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). |
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. |
Is there any chance of a |
Sure! |
Release PR is up: #94 |
It's released: https://crates.io/crates/hybrid-array/0.2.0 |
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.
The text was updated successfully, but these errors were encountered: