-
Notifications
You must be signed in to change notification settings - Fork 50
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
Stabalization - roadmap to v1.0 #157
Comments
Original discussion is in #60 but that issue is quite old and a bit stale. I've opened this one so that, if @apoelstra and @Kixunil are happy, we can close #60 to save others trawling through the stale stuff. There is a problem though with this, not everyone can edit the issue like the ones on I can just close this if its not an improvement over #60. |
@clarkmoody or @apoelstra please add a name: 1.0 |
Done. |
Oh I can't add labels to issues, even ones I wrote myself. |
:/. Do you remember offhand if there's a non-maintainer github role that would let you do that? |
@clarkmoody can we make @tcharding a "Triage" member here? I will do the same on rust-secp if you need, @tcharding . |
Yes please. |
Done! 😄 |
Thanks! |
I am good with stabilization as soon as is reasonable. |
Great! Now that error correction is done I believe this is the closest crate we have (in the |
Unfortunately it's "done" except for the user-facing API, which turn out to be the hardest part :) (though I don't think so). |
Tracking issue for what is needed for us to be able to stabalize the
bech32
crate.See also all issues marked with the
1.0
label: https://github.com/rust-bitcoin/rust-bech32/issues?q=is%3Aopen+is%3Aissue+label%3A1.0The text was updated successfully, but these errors were encountered: