The blog represents the software build and release versioning strategy which can be used to tag web or mobile releases with different version numbering schemes as illustrated later. The strategy can as well be used for software versioning.
A release version can be of type <major>.<minor>.<patch>.<buildnumber>. Following is what each of these keywords such as major, minor, patch and buildnumber represents:
Based on above, a major release can be 1.0.0.0. A hotfix release would go as 1.0.1.12 which means twelth build of hotfix release 1.0.1. Using buildnumber is optional. One can simply tag releases using format such as major.minor.patch. However, it provides greater visibility on the stability of release when tagged using format such as ….
An alternate versioning scheme used is <major>.<minor>.<patch>.<type>. Keyword type represents following:
The following strategy can be used to manage builds and releases with one of the version numbering schemes described in preceding sections:
In this blog, you would get to know the essential mathematical topics you need to…
This blog represents a list of questions you can ask when thinking like a product…
AI agents are autonomous systems combining three core components: a reasoning engine (powered by LLM),…
Artificial Intelligence (AI) has evolved significantly, from its early days of symbolic reasoning to the…
Last updated: 25th Jan, 2025 Have you ever wondered how to seamlessly integrate the vast…
Hey there! As I venture into building agentic MEAN apps with LangChain.js, I wanted to…