Skip to content
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 #662

Open
tcharding opened this issue Nov 1, 2023 · 8 comments
Open

Stabalization - roadmap to v1.0 #662

tcharding opened this issue Nov 1, 2023 · 8 comments

Comments

@tcharding
Copy link
Member

Tracking issue for what is needed for us to be able to stabalize the secp256k1 crate.

Issues we want resolved

Issues that might apply

@tcharding
Copy link
Member Author

Originally discussed in rust-bitcoin/rust-bitcoin#1392

@tcharding
Copy link
Member Author

@apoelstra please add a 1.0 label same as rust-bitcoin.

name: 1.0
color: #78BE0C
description: Issues and PRs required or helping to stabilize the API

@apoelstra
Copy link
Member

Done.

@tcharding
Copy link
Member Author

Thanks man

@Kixunil
Copy link
Collaborator

Kixunil commented Nov 15, 2023

FTR, I think this crate is not blocking stabilization of important bitcoin types since we could hide secp256k1::* types and operations and only expose them in serialized form or via extension traits. As such I suggest we focus most of our time at stabilizing relevant parts of bitcoin.

@tcharding
Copy link
Member Author

Yep sure thing, @apoelstra also told me offline that he didn't want to focus on secp at the moment. Mainly I was wanting to keeping on eye on secp so we don't do anything that we later have to change because of secp and for things that create/prove conventions (like error stuff etc.). I'll try a bit harder to stay away from here though :)

@apoelstra
Copy link
Member

FWIW "at the moment" just means "since I just had a baby". I don't mean to imply that I'm stepping away from this project or that I plan for it to be indefinitely stalled.

@tcharding
Copy link
Member Author

My bad, that was my understanding, i didn't mean to misrepresent you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants