Menu
I need a guideline or procedure which describe the version number policy for source code as per changes happened(major, minor, Micro), assigning particular version to release, labeling e.t.c
Your guideline in this regards will be highly appreciated....
374
There are simple rules that indicate when you must increment each of these versions: MAJOR is incremented when you make breaking API changes. MINOR is incremented when you add new functionality without breaking the existing API or functionality. PATCH is incremented when you make backwards-compatible bug fixes.
Major Version Number Updates When developers make significant changes to a software product's API, they will increment the major version number. This means that the changes are extreme, to the point that they render the software incompatible with older versions.
Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code.
You have some public interesting guidelines to get you started:
107
You might want to look at the Wikipedia article relating this, here it is: http://en.wikipedia.org/wiki/Version_number
29
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
