{"type":"rich","version":"1.0","author_name":"npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","author_url":"https://nostr.ae/npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-11-02\n🗒️ Summary of this message: The proposal is to let clients define the sub_version_num field as they wish, with a guideline suggestion to follow the IDENTIFIER VERSION format.\n📝 Original message:Point taken.\n\nAbout 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.\n\nThe 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.\n\nSo 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:\n\n\"Satoshi 0.5\"\n\nAlthough there would be little reason for this with a sane protocol versioning scheme.\n\nIf we're agreed then I'll start on that BIP.\n\n\n\n________________________________\nFrom: Gavin Andresen \u003cgavinandresen at gmail.com\u003e\nTo: Amir Taaki \u003czgenjix at yahoo.com\u003e\nSent: Wednesday, November 2, 2011 9:34 PM\nSubject: Re: [Bitcoin-development] Lock protocol version numbers\n\nGood idea.\n\nSounds perfect for a BIP....\n\nOn Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki \u003czgenjix at yahoo.com\u003e wrote:\n\u003e Hey,\n\u003e Can we lock the version numbers to be the protocol version (which changes\n\u003e rarely) and instead use the sub_version_num field + revision number for\n\u003e individual builds?\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111102/92391645/attachment.html\u003e"}