Pieter Wuille [ARCHIVE] on Nostr: 📅 Original date posted:2022-12-12 📝 Original message:Hi, After not even 10 ...
📅 Original date posted:2022-12-12
📝 Original message:Hi,
After not even 10 years of development, we'd like to announce the first tagged release of libsecp256k1, version 0.2.0:
https://github.com/bitcoin-core/secp256k1/releases/tag/v0.2.0
For a long time, libsecp256k1's development only had a master branch, creating unclarity about API compatibility and stability. Going forward, we will be creating tagged releases when relevant improvements are merged, following a semantic versioning scheme. This is not yet a version 1.0.0 as there are some important improvements we'd like to make before that point. We do reserve the ability to introduce API breaks, but promise clear documentation of such changes.
We're skipping version 0.1.0 because this version number was set in our autotools build scripts for years, and does not uniquely identify a set of source files. We will not be creating binary releases, but will take expected ABI compatibility issues into account for release notes and versioning.
The release tag is signed with my PGP key: https://bitcoin.sipa.be/sipa.asc
Grab it while it's hot. We welcome suggestions for the release process going forward.
Cheers,
--
the libsecp256k1 maintainers
📝 Original message:Hi,
After not even 10 years of development, we'd like to announce the first tagged release of libsecp256k1, version 0.2.0:
https://github.com/bitcoin-core/secp256k1/releases/tag/v0.2.0
For a long time, libsecp256k1's development only had a master branch, creating unclarity about API compatibility and stability. Going forward, we will be creating tagged releases when relevant improvements are merged, following a semantic versioning scheme. This is not yet a version 1.0.0 as there are some important improvements we'd like to make before that point. We do reserve the ability to introduce API breaks, but promise clear documentation of such changes.
We're skipping version 0.1.0 because this version number was set in our autotools build scripts for years, and does not uniquely identify a set of source files. We will not be creating binary releases, but will take expected ABI compatibility issues into account for release notes and versioning.
The release tag is signed with my PGP key: https://bitcoin.sipa.be/sipa.asc
Grab it while it's hot. We welcome suggestions for the release process going forward.
Cheers,
--
the libsecp256k1 maintainers