...
Every push to master should increment the release number in some fashion. For example, if OpenLMIS is at 2.1.5, a single bug fix pushed to master would change the number to 2.1.6. Final decisions on any number change lies with the Tech and Product groups.
The version number is displayed on the login page, following the format above and includes the build number and build name. Specifically, the form is: vMAJOR.MINOR.PATCH buildNumber-buildName, where buildNumber and buildName correspond to the name of the Jenkins build and corresponding build number. For example, "v2.0.1 14-stable".
For discussion on this topic, see this thread.