Published “SemVer Branching” article
To start a flame war one just needs to post an article on code formatting. Or a branching strategy. But we are not going to start the war here, aren’t we? Any new ideas are welcome and if there is a better way, let’s read about it.
Today I published the second installment on the software process I use in my projects. This article is about branching.
Semantic Versioning or SemVer is a popular way to identify versions of software. It is mandated in some package managers, such as NPM, and widely used in the projects utilizing the build tools not mandating it. In some cases, even though the versioning scheme used by the package manager is not fully compatible with SemVer, the teams opt not to follow it in spirit. It just works.
It only makes sense to have a branching strategy that is specifically designed to work with SemVer. This article is a description of such a strategy. I use it in the software projects I manage, and I’m pretty content with it.