Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=decker.christian@gmail.com;
	helo=mail-ww0-f53.google.com; 
MIME-Version: 1.0
In-Reply-To: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Wed, 2 Nov 2011 22:32:10 +0100
Message-ID: <CALxbBHXOO+p40Q_j7sPK+cG1yGyDWo3fT2_Nd8xhsWmoXD5LNA@mail.gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=0015174481ecbbc7d804b0c7368e
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Precedence: list

--0015174481ecbbc7d804b0c7368e
Content-Type: text/plain; charset=ISO-8859-1

I don't really get what you want to achieve with this. The protocol will be
slow down evolution (hopefully) soon, while the clients will continue
releasing at a similar rhythm. It took long enough to decouple the protocol
version from being bumped each client release, now doing the inverse
coupling makes no sense.

Regards,
Chris
On Wed, Nov 2, 2011 at 10:23 PM, Amir Taaki <zgenjix@yahoo.com> wrote:

> Hey,
>
> Can we lock the version numbers to be the protocol version (which changes
> rarely) and instead use the sub_version_num field + revision number for
> individual builds?
>
> Satoshi 0.4
> BitcoinJava 120311
> bitcoin-js 6
>
> Like so. Otherwise we will have version bumping insanity :)
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

--0015174481ecbbc7d804b0c7368e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I don&#39;t really get what you want to achieve with this. The protocol wil=
l be slow down evolution (hopefully) soon, while the clients will continue =
releasing at a similar rhythm. It took long enough to decouple the protocol=
 version from being bumped each client release, now doing the inverse coupl=
ing makes no sense.<br>

<br>Regards,<br>Chris<br><div class=3D"gmail_quote">On Wed, Nov 2, 2011 at =
10:23 PM, Amir Taaki <span dir=3D"ltr">&lt;<a href=3D"mailto:zgenjix@yahoo.=
com">zgenjix@yahoo.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">

<div><div style=3D"color:#000;background-color:#fff;font-family:times new r=
oman, new york, times, serif;font-size:12pt"><div>Hey,</div><div><br></div>=
<div>Can we lock the version numbers to be the protocol version (which chan=
ges rarely) and instead use the sub_version_num field + revision number for=
 individual builds?</div>

<div><br></div><div>Satoshi 0.4</div><div>BitcoinJava 120311</div><div>bitc=
oin-js 6</div><div><br></div><div>Like so. Otherwise we will have version b=
umping insanity :)</div></div></div><br>-----------------------------------=
-------------------------------------------<br>


RSA(R) Conference 2012<br>
Save $700 by Nov 18<br>
Register now<br>
<a href=3D"http://p.sf.net/sfu/rsa-sfdev2dev1" target=3D"_blank">http://p.s=
f.net/sfu/rsa-sfdev2dev1</a><br>___________________________________________=
____<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br>

--0015174481ecbbc7d804b0c7368e--