public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Date: Wed, 2 Nov 2011 15:33:12 -0700 (PDT)	[thread overview]
Message-ID: <1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2232 bytes --]

  parent reply	other threads:[~2011-11-02 22:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 21:23 [Bitcoin-development] Lock protocol version numbers Amir Taaki
2011-11-02 21:32 ` Christian Decker
     [not found] ` <CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
2011-11-02 22:33   ` Amir Taaki [this message]
2011-11-02 22:42     ` Christian Decker
2011-11-02 22:58       ` Amir Taaki
2011-11-02 22:46     ` Luke-Jr
2011-11-02 22:55       ` Amir Taaki
2011-11-02 23:07         ` Luke-Jr
2011-11-02 23:22           ` Christian Decker
2011-11-03  4:46             ` Jeff Garzik
2011-11-05 14:32 ` Mike Hearn
2011-11-05 14:45   ` Christian Decker
     [not found]     ` <1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
2011-11-05 15:39       ` Amir Taaki
2011-11-05 16:17         ` Christian Decker
2011-11-05 16:29           ` Luke-Jr
2011-11-05 16:40             ` Amir Taaki
2011-11-05 17:30               ` Jordan Mack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1320273192.94365.YahooMailNeo@web121014.mail.ne1.yahoo.com \
    --to=zgenjix@yahoo.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox