I don&#39;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.<br>

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

<div><div style="color:#000;background-color:#fff;font-family:times new roman, 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 changes 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>bitcoin-js 6</div><div><br></div><div>Like so. Otherwise we will have version bumping insanity :)</div></div></div><br>------------------------------------------------------------------------------<br>


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