Managing versions of the application
All the options that we presented earlier provide version management mechanisms. Version management is as important as the packaging and distribution mechanism that we select.
As our application evolves and new features are added, modified, or removed, we want to offer a way for our users to consume these updates at their convenience. That is where versioning comes into play.
Currently, only a single version of our application is distributed. We can hence install it by either omitting its version number or explicitly indicating it.
But what if we update the application? How can we distribute the new version? And what if the new version introduces a bug and we need to roll back to the previous version?
Let’s explore how we can achieve this for each of the distribution methods that we covered earlier.
Semantic versioning primer
Before we dive into managing different versions of an application, let us start by introducing semantic...
