1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Return-Path: <bitcoin-dev@wuille.net>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 88675C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Dec 2022 22:47:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 62FB040256
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Dec 2022 22:47:19 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 62FB040256
Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=wuille.net header.i=@wuille.net header.a=rsa-sha256
header.s=protonmail3 header.b=c3Xt5xoE
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id YzOTknRxCWJ4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Dec 2022 22:47:18 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 12CEA40002
Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23])
by smtp2.osuosl.org (Postfix) with ESMTPS id 12CEA40002
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 12 Dec 2022 22:47:16 +0000 (UTC)
Date: Mon, 12 Dec 2022 22:47:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wuille.net;
s=protonmail3; t=1670885234; x=1671144434;
bh=mURWynK8eKa6qv66sB6vWHmkLAAYvzutBLiLuiEy45M=;
h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date:
Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector;
b=c3Xt5xoEBuu2g2DcpgRmuGzq9PgrcppYNDWdyW863W1w02CdtYg+cvG9Gl9QURzKm
NResQgqjhxnHwLpcC0rrY02mMywTHdoks4BxCPZ++XzwsxI+Ayb5/Xmi18AKUUMh/A
cnJdWLzOPdfpEgyXe/BKVYIPWXGX4t/IT8q+b7crRi8RFOYcGNkx08Hsv9pBZUlabQ
O0zWd+1B5Q36ayvYzXK2heT1XCc2tMsjKTY9up/k2oG5mt7RQmPk1HIgZ5A8KSrWZq
2CUotcQKJPwqlWoFUNo0BtFwTjNkDld68z621n9yZXAErOmzWYjxF8Aj+ay2pxX3a0
1yQF9hEs+YfOA==
To: Bitcoin dev list <bitcoin-dev@lists.linuxfoundation.org>
From: Pieter Wuille <bitcoin-dev@wuille.net>
Message-ID: <v-5cMoyHzxi0ZUUECBV_l_87TwzxBXr7-aIMrjC5taolnlKi256ZFnoH6EGw4MpvwVwAJkBwhPToRfSp1DFK314O7edTwjKndQ0azBRGfgI=@wuille.net>
Feedback-ID: 19463299:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 12 Dec 2022 22:49:45 +0000
Subject: [bitcoin-dev] libsecp256k1 version 0.2.0 released
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2022 22:47:19 -0000
Hi,
After not even 10 years of development, we'd like to announce the first tag=
ged release of libsecp256k1, version 0.2.0:
=C2=A0 =C2=A0 https://github.com/bitcoin-core/secp256k1/releases/tag/v0.2.0
For a long time, libsecp256k1's development only had a master branch, creat=
ing unclarity about API compatibility and stability. Going forward, we will=
be creating tagged releases when relevant improvements are merged, followi=
ng a semantic versioning scheme. This is not yet a version 1.0.0 as there a=
re some important improvements we'd like to make before that point. We do r=
eserve 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 aut=
otools build scripts for years, and does not uniquely identify a set of sou=
rce 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 goin=
g forward.
Cheers,
--=20
the libsecp256k1 maintainers
|
