Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

DevOps: Semantic Versioning Simplified

DZone's Guide to

DevOps: Semantic Versioning Simplified

Semantic versioning allows you to easily deal with features and fixes across a variety of environments so that you can avoid dependency hell.

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

Semantic versioning makes it easy and convenient to track, test, deploy, patch, and roll back features, enhancements, bugs, and fixes across a variety of environments in the software supply chain.

Semantic versioning provides an efficient and effective framework to version the software products so that the infamous dependency hell can be avoided.

What Is Semantic Versioning?

Semantic versioning uses the MAJOR.MINOR.PATCH number scheme for software products. For example:

Semantic_Versioning

How to Decide When to Update the Numbers

You should increment the PATCH number during the following circumstances:

  • A backward compatible bug fix.

  • A backward compatible maintenance release.

  • A backward compatible hot-fix.

You should increment the MINOR number in these situations (note that PATCH should be reset to zero when MINOR is incremented):

  • A backward compatible new framework adoption.

  • A backward compatible new functionality implementation.

  • A backward compatible framework enhancement.

  • A backward compatible functionality enhancement.

Finally, you should increment the MAJOR number in the following events (again, note that PATH and MINOR should both be reset to zero when MAJOR is incremented):

  • Any backward incompatible change.

  • A situation in which the MAJOR zero (0.Y.Z) should be considered for development. The product shouldn't be considered stable and should not be deployed on production.

What About Versioning During Continuous Integration?

Prerelease numbers with semantic versioning can tackle the problem of versioning during CI (for example: X.Y.Z-${CI_BUILD_NUMBER}, 2.0.5-1992).

Once the software product is ready, the prerelease number should be removed and the product should be published and released to the external repository.

Finally, note that once the package is released and published, it must not be modified. Any modifications must absolutely be released as a new version.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:
devops ,semantic versioning ,continuous integratinon ,software development

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}