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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
Return-Path: <marcel@jamin.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 57B431851
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 09:06:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com
[209.85.160.177])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A3FA712E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 09:06:00 +0000 (UTC)
Received: by ykdz138 with SMTP id z138so72701029ykd.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 01 Oct 2015 02:06:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=Cof9JcDGM5HsAWUo5UqUmBfS/BqaLomnuNG6hkXpvBc=;
b=i5AkA2xO+RzkHd+TD6pOHXdXapUzRt5L4BaO9lXN6suueDaa4pslplor8rozSwOqwt
c7stVwiVD+AApszBn1Zn/RE3wBKgG6UiAX8hwUY3PrFXa2wsnN5QVdygPZay4ip+91uq
KojHTeqgqqAVZqMfGiW+1zZ0TRRKg/A3Gl3SvbVKmIHt7aDrJd5r1aGIcWU7pBE9QiEz
kXBJYpMCoIhDglK0UuyLgyUMiSVMSkfoYGlrHV9ZzoGj6qS8ph6YoUQHlAV7eCeNGfcC
SDtBJSiEUxObKUg3RLDU6EY13I9PqmO7bdFcSD+ywI0LJ+pusjs4TVR9xp+qMOormNQy
kEdw==
X-Gm-Message-State: ALoCoQnN8ESm3dmvbtp6M+BK+DIFY7hkffASxMxUseYX8tvRvSbSa1F+lyYasCXuKVb22lLY6TYy
MIME-Version: 1.0
X-Received: by 10.170.173.1 with SMTP id p1mr6814908ykd.101.1443690359807;
Thu, 01 Oct 2015 02:05:59 -0700 (PDT)
Received: by 10.13.220.65 with HTTP; Thu, 1 Oct 2015 02:05:59 -0700 (PDT)
In-Reply-To: <20151001085058.GA10010@amethyst.visucore.com>
References: <20150924112555.GA21355@amethyst.visucore.com>
<201509301757.44035.luke@dashjr.org>
<20151001085058.GA10010@amethyst.visucore.com>
Date: Thu, 1 Oct 2015 11:05:59 +0200
Message-ID: <CAAUq486=TisNp0MbFjWYdCsyVX-qx5dV_KKZuNR7Jp63KNWeiQ@mail.gmail.com>
From: Marcel Jamin <marcel@jamin.net>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ac04410168e0521075b57
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Thu, 01 Oct 2015 09:06:01 -0000
--001a113ac04410168e0521075b57
Content-Type: text/plain; charset=UTF-8
Any particular reason bitcoin versioning doesn't follow the SemVer spec?
2015-10-01 10:50 GMT+02:00 Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org>:
> On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:
> > On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
> > bitcoin-dev wrote:
> > > 2015-12-01
> > > -----------
> > > - Feature freeze
> >
> > Where is "Consensus freeze"? Shouldn't this be put off until after the HK
> > workshop in case a hardfork is decided on? Or have we de-coupled it from
> the
> > release process entirely anyway (since old versions need an update for it
> > too)?
>
> In principle, "feature freeze" means that any large code changes will no
> longer go into 0.12, unless fixing critical bugs.
>
> I'm not keen on postponing 0.12 for such reasons - after the HK workshop
> I'm sure that it will take some development/testing/review before code
> makes it into anything. Apart from that there's a good point to decouple
> consensus changes from Bitcoin Core major releases.
>
> We've seen lot of release date drift due to "this and this change needs to
> make it in" in the past, that was a major reason to switch to a time-based
> instead of feature-based release schedule.
>
> We can always do a 0.12.1.
>
> Wladimir
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a113ac04410168e0521075b57
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Any particular reason bitcoin versioning doesn't follo=
w the SemVer spec?<br></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">2015-10-01 10:50 GMT+02:00 Wladimir J. van der Laan via bitcoin-=
dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></sp=
an>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">On Wed, Sep 30, 2015 at 05:57:42PM +=
0000, Luke Dashjr wrote:<br>
> On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan v=
ia<br>
> bitcoin-dev wrote:<br>
> > 2015-12-01<br>
> > -----------<br>
> > - Feature freeze<br>
><br>
> Where is "Consensus freeze"? Shouldn't this be put off u=
ntil after the HK<br>
> workshop in case a hardfork is decided on? Or have we de-coupled it fr=
om the<br>
> release process entirely anyway (since old versions need an update for=
it<br>
> too)?<br>
<br>
In principle, "feature freeze" means that any large code changes =
will no longer go into 0.12, unless fixing critical bugs.<br>
<br>
I'm not keen on postponing 0.12 for such reasons - after the HK worksho=
p I'm sure that it will take some development/testing/review before cod=
e makes it into anything. Apart from that there's a good point to decou=
ple consensus changes from Bitcoin Core major releases.<br>
<br>
We've seen lot of release date drift due to "this and this change =
needs to make it in" in the past, that was a major reason to switch to=
a time-based instead of feature-based release schedule.<br>
<br>
We can always do a 0.12.1.<br>
<br>
Wladimir<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div><br></div>
--001a113ac04410168e0521075b57--
|
