Version? #396

1. 
   alexreg commented at 1:54 am on May 14, 2016: none

   Is there any reason that no versions have been tagged or actual releases made for this library, yet?
2. 
   afk11 commented at 1:43 pm on May 14, 2016: contributor

   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.
3. 
   alexreg commented at 2:39 pm on May 14, 2016: none

   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 notifications@github.com 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)

4. 
   apoelstra commented at 5:23 pm on May 16, 2016: contributor

   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.

5. 
   gmaxwell commented at 7:44 pm on May 16, 2016: contributor

   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.
6. 
   alexreg commented at 2:02 am on May 17, 2016: none

   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.
7. 
   chfast commented at 3:45 pm on September 7, 2016: none

   Can you create a milestone to track this list of pending tasks?
8. 
   afk11 commented at 10:12 am on November 19, 2016: contributor

   @gmaxwell any updates on publishing yet? Really wondering when this issue will be closed, this one is related also: #286
9. 
   sipa commented at 5:24 am on November 28, 2016: contributor

   Closing in favor of #286.
10. sipa closed this on Nov 28, 2016

    ---

11. afk11 cross-referenced this on Jan 6, 2020 from issue Create a release by shazow

Contributors
alexreg afk11 apoelstra gmaxwell chfast sipa