References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
Message-ID: <1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com>
Date: Wed, 2 Nov 2011 15:33:12 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="-594111766-1714674839-1320273192=:94365"
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>

---594111766-1714674839-1320273192=:94365
Content-Type: text/plain; charset=us-ascii

Point taken.

About the sub_version_num though. I prefer to let the field by defined clients however they wish, with just a guideline suggestion that IDENTIFIER VERSION is a format they should follow.

The idea being that different projects would have different release scheduling schemes and it'd be restrictive to lock people into the popular major.minor system.

So for the current bitcoin to find out the version number of other clients (if it was needed), it would have to parse the number from the string:

"Satoshi 0.5"

Although there would be little reason for this with a sane protocol versioning scheme.

If we're agreed then I'll start on that BIP.


________________________________
From: Gavin Andresen <gavinandresen@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Sent: Wednesday, November 2, 2011 9:34 PM
Subject: Re: [Bitcoin-development] Lock protocol version numbers

Good idea.

Sounds perfect for a BIP....

On Wed, Nov 2, 2011 at 5: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?

-- 
--
Gavin Andresen
---594111766-1714674839-1320273192=:94365
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Point taken.</span></div><div><br><span></span></div><div><span>About the sub_version_num though. I prefer to let the field by defined clients however they wish, with just a guideline suggestion that IDENTIFIER VERSION is a format they should follow.</span></div><div><br><span></span></div><div><span>The idea being that different projects would have different release scheduling schemes and it'd be restrictive to lock people into the popular major.minor system.</span></div><div><br><span></span></div><div><span>So for the current bitcoin to find out the version number of other clients (if it was needed), it would have to parse the number from the string:</span></div><div><br><span></span></div><div><span>"Satoshi 0.5"</span></div><div><br><span></span></div><div><span>Although there would be little reason for this with
 a sane protocol versioning scheme.</span></div><div><br><span></span></div><div><span>If we're agreed then I'll start on that BIP.</span></div><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Gavin Andresen &lt;gavinandresen@gmail.com&gt;<br><b><span style="font-weight: bold;">To:</span></b> Amir Taaki &lt;zgenjix@yahoo.com&gt;<br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, November 2, 2011 9:34 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Bitcoin-development] Lock protocol version numbers<br></font><br>
Good idea.<br><br>Sounds perfect for a BIP....<br><br>On Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki &lt;<a ymailto="mailto:zgenjix@yahoo.com" href="mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>&gt; wrote:<br>&gt; Hey,<br>&gt; Can we lock the version numbers to be the protocol version (which changes<br>&gt; rarely) and instead use the sub_version_num field + revision number for<br>&gt; individual builds?<br><br>-- <br>--<br>Gavin Andresen<br><br><br></div></div></div></body></html>
---594111766-1714674839-1320273192=:94365--