Worsening
Two days, ago I made a blog post documenting my feelings about SemVer. It wasn’t anything special, just conveying an idea about version numbering being a lot more opinionated and conveying more to software consumers. Well, I have now released the first version of ISAA to the public, under this alternative versioning system. Therefore, I actually need to name it. If you saw, version numbers are preappended with a literal ‘w’, this is due to the original thought of a name being Temantic Wersioning.
The Worsening Versioning Number System You can read my initial blog post here.
Formal Specification I have not gotten around to making a formal specification for the worsening, but I will soon enough.
Projects That Utilize Worsening Interior Sergeant-At-Arms, A Simple Singleton Process Manager Contact If you have questions about implementing worsening or you would like your project utilizing worsening to be featured. you may email me @ worsening@robertismo.com.
Semantic Versioning(SemVer) is a version number system that proposes a simple versioning scheme: v<MAJOR>.<MINOR>.<PATCH>[<ADDITIONAL>](I will prepend a literal v when referring to a SemVer number). Straight from their page:
MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixes An example of a SemVer is v1.11.3, or v0.0.3.
What is wrong here? Semantic versioning is pretty good!