Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
util-1.0.0, util-2.0.0, util-3.0.0, bridge-impl-2.0.0, bridge-impl-3.0.0, bridge-ext-1.0.0, bridge-ext-2.0.0, bridge-ext-3.0.0, bridge-ext-5.0.0, bridge-impl-4.0.0, bridge-impl-5.0.0, bridge-ext-7.0.0
-
None
Description
{markdown}
[Semantic versioning uses the major.minor.patch version scheme.](http://semver.org/) After doing a few google searches, it seems that major.minor.patch is the most popular version scheme:
"major.minor.patch" : About 41,600 results
"major.minor.build" : About 25,100 results
"major.minor.revision" : About 19,000 results
"major.minor.micro" : About 13,200 results
"major.minor.bugfix" : About 9,980 results
Util's `Product` API should be changed to reflect this version scheme. Specifically `Product.getRevisionVersion()` to `Product.getPatchVersion()`.{markdown}
[Semantic versioning uses the major.minor.patch version scheme.](http://semver.org/) After doing a few google searches, it seems that major.minor.patch is the most popular version scheme:
"major.minor.patch" : About 41,600 results
"major.minor.build" : About 25,100 results
"major.minor.revision" : About 19,000 results
"major.minor.micro" : About 13,200 results
"major.minor.bugfix" : About 9,980 results
Util's `Product` API should be changed to reflect this version scheme. Specifically `Product.getRevisionVersion()` to `Product.getPatchVersion()`.{markdown}