{"type":"rich","version":"1.0","author_name":"npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn","author_url":"https://nostr.ae/npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuyn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-11-02\n🗒️ Summary of this message: A proposal to lock version numbers to the protocol version and use the sub_version_num field for individual builds was discussed.\n📝 Original message:Just for reference: https://github.com/bitcoin/bitcoin/pull/63\nThe issue resulted in my most useless pull request fixing two variables :-)\n\nI second the use of sub_version_num as a Client and Version identifier.\n\nRegards,\nChris\n\nOn Wed, Nov 2, 2011 at 11:33 PM, Amir Taaki \u003czgenjix at yahoo.com\u003e wrote:\n\n\u003e Point taken.\n\u003e\n\u003e About the sub_version_num though. I prefer to let the field by defined\n\u003e clients however they wish, with just a guideline suggestion that IDENTIFIER\n\u003e VERSION is a format they should follow.\n\u003e\n\u003e The idea being that different projects would have different release\n\u003e scheduling schemes and it'd be restrictive to lock people into the popular\n\u003e major.minor system.\n\u003e\n\u003e So for the current bitcoin to find out the version number of other clients\n\u003e (if it was needed), it would have to parse the number from the string:\n\u003e\n\u003e \"Satoshi 0.5\"\n\u003e\n\u003e Although there would be little reason for this with a sane protocol\n\u003e versioning scheme.\n\u003e\n\u003e If we're agreed then I'll start on that BIP.\n\u003e\n\u003e ------------------------------\n\u003e *From:* Gavin Andresen \u003cgavinandresen at gmail.com\u003e\n\u003e *To:* Amir Taaki \u003czgenjix at yahoo.com\u003e\n\u003e *Sent:* Wednesday, November 2, 2011 9:34 PM\n\u003e *Subject:* Re: [Bitcoin-development] Lock protocol version numbers\n\u003e\n\u003e Good idea.\n\u003e\n\u003e Sounds perfect for a BIP....\n\u003e\n\u003e\n\u003e On Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki \u003czgenjix at yahoo.com\u003e wrote:\n\u003e \u003e Hey,\n\u003e \u003e Can we lock the version numbers to be the protocol version (which changes\n\u003e \u003e rarely) and instead use the sub_version_num field + revision number for\n\u003e \u003e individual builds?\n\u003e\n\u003e --\n\u003e --\n\u003e Gavin Andresen\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e RSA(R) Conference 2012\n\u003e Save $700 by Nov 18\n\u003e Register now\n\u003e http://p.sf.net/sfu/rsa-sfdev2dev1\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111102/6ae2fbe3/attachment.html\u003e"}