AnsweredAssumed Answered

Custom Version Label Policy

Question asked by toppac on Nov 4, 2009
Latest reply on Feb 15, 2016 by parashiftaustralia
I'd like to change the default versioning policy. Rather than doing a 1.1, 1.2 notation I'd like every version to be a major version change, so 1, 2, 3, etc. I found in the docs there is some mention on it

Generally this version number is only used internally, it is the version label that used publicly to identify the version.

The version label is calculated from the version number and gives, within the scope of the version history, a unique label for the version. It is this label that is placed in the versionable aspect to indicate the related current version for a node.

The generation of the version label can be customized by creating a version label policy behaviour and registering it in place of the default version label policy. This gives applications flexability to determine their own version labeling policies.

The default version label policy uses 1.1, 1.2, style of progressive version labels, moving to 2.0 if the version is considered to be a major change. This is indicated in the version meta data which the version label policy has access to.

For more information on policies see <insert the URL here>

But I have yet to find a good explanation of how to configure this. Can anyone give me an example of how to change the version label policy?