svn - How to measure software component maturity by processing version numbers? -
i'm trying implement metric describes how mature/stable software component looking @ how many versions have been made of in time frame (or starting date).
more versions indicate less mature/stable component. not accurate: when looking @ larger time frame, component might've had many changes @ beginning, few recently. indicates stable component. also, version numbering should factored in. change '1.4' '2.0' should more significant change '1.4.1' '1.4.2'.
in nutshell: older changes should matter less, higher increase in version number should matter more.
is there industry standard weight function achieve desired result according these criteria? or should attempt create own?
have @ semantic versioning:
given version number major.minor.patch, increment the: major version when make incompatible api changes, minor version when add functionality in backwards-compatible manner, , patch version when make backwards-compatible bug fixes. additional labels pre-release , build metadata available extensions major.minor.patch format. in addition, use fourth number revision svn revision of build package created source code @ revision. update assembly versions of components number during build, e.g:
2.0.3.xyz
hope helps.
Comments
Post a Comment