Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

[Discussion] Standardize Versioning Scheme?

Would you like versioning to be standardized?

  • Yes

    Votes: 0 0.0%
  • No

    Votes: 0 0.0%

  • Total voters
    0
Joined
Nov 18, 2013
Messages
120
I was just briefly thinking on this. Versioning is in place but I don't think it means much to people as of right now. While most might think it a moot point, I feel it is important to easily convey what changes/states a bot is at very easily for members. I think due to that, it would benefit from having a standard. For example version 1.2.12 would mean

1: Major Feature release
2: Minor Feature release
12: Bug fixes

If this exists, please excuse my ignorance! Also if this is the wrong place to post these, could you please kindly move it elsewhere.
 
Joined
Dec 10, 2014
Messages
3,332
That's the version standard that I use haha
Although I feel that giving the example 1.2.3 would convey your point easier

Either way, I kind of feel like the author should have freedom of choice when dealing with their versioning :p
 
Last edited:
Engineer
Joined
Jul 28, 2013
Messages
2,776
I was just briefly thinking on this. Versioning is in place but I don't think it means much to people as of right now. While most might think it a moot point, I feel it is important to easily convey what changes/states a bot is at very easily for members. I think due to that, it would benefit from having a standard. For example version 1.2.12 would mean

1: Major Feature release
2: Minor Feature release
12: Bug fixes

If this exists, please excuse my ignorance! Also if this is the wrong place to post these, could you please kindly move it elsewhere.
That's the versioning scheme we've publicly stated we've supported in the past and hence why in the manifest example it is used.
 
Top