Create a release

[shazow]

I'm trying to add a homebrew install recipe for secp256k1 (Homebrew/legacy-homebrew#42605) but they require a specific tagged version to include in the mainline tap. Any chance we can tag some commit(s) with some version scheme?

[sipa]

We're currently still considering this code experimental, and don't have releases or API compatibility yet.

This will hopefully change soon.

[shazow]

Fair enough. Please ping the above issue when you're ready and we can update the recipe. :)

[sipa]

I'll leave this issue open until then.

[lukateras]

Or you could just cut a v0.x tag.

[dcousens]

@shazow you can't use a commit hash?

[shazow]

@dcousens Correct. It's a homebrew requirement.

[gmaxwell]

It's a good requirement. You should not be shipping split out libsecp256k1. The software is not released, the API is highly unstable, etc. We will release when it's ready for that.

[afk11]

I noticed this library is being built and shipped in debian/stretch. I've asked in #secp256k1 and #bitcoin-core-dev but no-one seems to be claiming it. Emailed the Debian Bitcoin Team to see what the story is.. https://packages.debian.org/stretch/libsecp256k1-0

[sugarjig]

I tried to create a homebrew formula for libbitcoin-explorer, and it has a transitive dependency on this library. I imagine that this issue is blocking lots of other projects from creating homebrew formulae. It's been exactly 2 years since this issue was opened. Are we any closer to a tagged release?

[afk11]

My update to the above is that whoever packages groestlecoin & bitcoin into debian (contact details are on the link above) is maintaining the package somewhat, but I don't trust the build.

@sugarjig For now can you specify a git commit when pulling in dependencies?