Proposal for a New Build Numbering Scheme #5296
Description
Hello,
I've noticed (and I'm sure I'm not the only one) that the current build version doesn't align with the protocol version. This creates unnecessary confusion; for example, a Casper Node build on the testnet with version 2.0.0-a7e4ff1 is actually a 2.0.1 version.
I'd like to propose a proper solution to this issue.
Proposal for a New Build Numbering Scheme
Currently, the build version syntax is as we've seen. My proposal is to replace this with ProtocolVersion-commitID. Using the example from above, this would become 2.0.1-a7e4ff1.
What would this small change achieve?
It would make it much easier to manage builds for a specific protocol version. Developers could modify and optimize the software within a single protocol version without confusion.
It would significantly reduce the current chaos and make versioning more intuitive for everyone.
Additional i have a question, why 2.0.1 for testnet = mainnet 2.0.0 and both has same build version? Or someone did mistake with publish version or i dont get it.