Tag a release #820

1. 
   luke-jr commented at 2:49 pm on September 18, 2020: member

   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?

2. 
   real-or-random commented at 3:03 pm on September 18, 2020: 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. )

3. real-or-random closed this on Sep 18, 2020

   ---

4. 
   luke-jr commented at 7:30 pm on September 18, 2020: member

   Basically -version in LDFLAGS

Contributors
luke-jr real-or-random