SphereCommunity
Versioning - Printable Version

+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: General Discussion (/Forum-General-Discussion)
+--- Forum: UO/Sphere Discussion (/Forum-UO-Sphere-Discussion)
+--- Thread: Versioning (/Thread-Versioning)



Versioning - Khaos - 05-02-2012 10:16 PM

This is more of an informative post than anything. Hopefully it will set new standards.

A couple weeks ago I became quite inquisitive on how versioning is standardized. I read several articles on versioning online from wiki sites, to programming sites, etc.

What I found really made me distraught. There is no real standard. I figured I could find something we could all use with our scripts and systems we design.

After reviewing the sites several times and making notes on what was important and unimportant in versioning and what the common versus uncommon versioning means; I pieced together my own versioning which seems more logical than anything I read.

I would like to share this new standard I now use. It is a 4 digit versioning which makes perfect sense to me, and Ben appreciated it too.

version #1.#2.#3.#4 or v#1.#2.#3.#4

#1: The first digit is used for the initial release version of a stable build. This number should be updated further when enough significant major additions or changes are added that you feel it could be a whole new release. As we call them, a re-release. This is definitely important to a user.

#2: The second digit is used for major bug fixes and additions to your code. This should be updated to show critical bug fixes or a huge addition to the code which would make a significant difference for the user. THis would be important to a user.

#3: The third digit is used for any minor bug fixes or minor additions you add to your code. This is useful if you post several versions of code. As some people might not worry about a minor fix or change.

#4: The fourth digit is used for documentation or revisions updating in your script or attached readme.txt files or a .doc (examples). This # will reflect any changes you made in your documentation. Whether it is a revisions list, usage, etc.


I actually hope people find this useful. If some one would like, I can toss up the links to everything I read. I am sure it will waste your time as it did mine.


RE: Versioning - Crusader - 05-02-2012 10:19 PM

i also agree with this. thumbs up.