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.

Sign up for GitHub

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

Jump to bottom

Tag a release #820

Closed
luke-jr opened this issue Sep 18, 2020 · 2 comments
Closed

Tag a release #820

luke-jr opened this issue Sep 18, 2020 · 2 comments

Comments

@luke-jr
Copy link
Member

luke-jr commented Sep 18, 2020

libsecp256k1 is fairly mature these days. It seems like it would be appropriate to begin versioning the API/ABI and tagging releases.

Already, configure warns that experimental APIs don't have stable APIs, which implies that non-experimental features do.

If you want, I can prepare a PR to setup the necessary autotools stuff.

Also need to select an initial version number. Does 1.0 sound good?
@real-or-random
Copy link
Contributor

There's agreement here that we should have a tagged release soon, see the most recent comments in #286.

If you want, I can prepare a PR to setup the necessary autotools stuff.

What would be the necessary autotools stuff?

(I'm closing this since it's essentially a duplicate of #286, feel free to reply there. )

@luke-jr
Copy link
Member Author

luke-jr commented Sep 18, 2020

Basically -version in LDFLAGS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@real-or-random @luke-jr