MIME-Version: 1.0
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
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
Precedence: list

--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&#39;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">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</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>
&gt; On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan v=
ia<br>
&gt; bitcoin-dev wrote:<br>
&gt; &gt; 2015-12-01<br>
&gt; &gt; -----------<br>
&gt; &gt; - Feature freeze<br>
&gt;<br>
&gt; Where is &quot;Consensus freeze&quot;? Shouldn&#39;t this be put off u=
ntil after the HK<br>
&gt; workshop in case a hardfork is decided on? Or have we de-coupled it fr=
om the<br>
&gt; release process entirely anyway (since old versions need an update for=
 it<br>
&gt; too)?<br>
<br>
In principle, &quot;feature freeze&quot; means that any large code changes =
will no longer go into 0.12, unless fixing critical bugs.<br>
<br>
I&#39;m not keen on postponing 0.12 for such reasons - after the HK worksho=
p I&#39;m sure that it will take some development/testing/review before cod=
e makes it into anything. Apart from that there&#39;s a good point to decou=
ple consensus changes from Bitcoin Core major releases.<br>
<br>
We&#39;ve seen lot of release date drift due to &quot;this and this change =
needs to make it in&quot; 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--