Version?

[alexreg]

Is there any reason that no versions have been tagged or actual releases made for this library, yet?

[afk11]

Largely because the API changed so frequently! That hasn't happened for a year or so now, so I'm starting to get curious as well.

[alexreg]

Yes, that’s been my thoughts too. I believe the API has been pretty stable recently, so it would be nice to have a proper release, like a 0.1.0 at least.

On 14 May 2016, at 14:43, Thomas Kerin [email protected] wrote:

Largely because the API changed so frequently! That hasn't happened for a year or so now, so I'm starting to get curious as well.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #396 (comment)

[apoelstra]

The plan is not to have any versions until the symbolic "1.0" release, after which we stop breaking stuff all the time (and use semantic versioning so that any breaks that do happen won't wreck people's stuff).

There are still a few tasks pending before 1.0 -- on my plate, getting the low-order-curve exhaustive tests complete and merged. But also more serious things like finalizing the Schnorr signature API.

We had planned to have this done a while ago, but all of the primary developers on this project have been extremely busy for the last several months.

[gmaxwell]

Actually documenting and publishing on many of the (potentially risky) novel optimization we use is something I consider a requirement before considering a published version here.

[alexreg]

Thanks for clarifying, @apoelstra. I look forward to the day it is standardised! I didn't realise quite how original some of this library's implementation was.

[chfast]

Can you create a milestone to track this list of pending tasks?

[afk11]

@gmaxwell any updates on publishing yet? Really wondering when this issue will be closed, this one is related also: #286

[sipa]

Closing in favor of #286.