For an explanation of Cohero's versioning logic, please consult this article:
When users want to release a new version of an asset, the release journey asks them about the type of update it represents.
Why does Cohero want me to choose the type?
Effectively, Cohero wants to classify the significance of their update, because the choice (either Major or Minor) informs the right version numbering that this new version will get.
Let's explain with an example. We started with an available Version 1.0. At some point, our user decides that he wants to create a new version for that - so a '(New Version) Draft is what he starts, and gets to work on. After a while, that draft is ready to be released. At that point, just how significant his changes have been, is known only to the user who managed or made the update. But the versioning logic needs to know too (so that eventually the rest of the workspace understands it too).
What are major and minor updates?
Cohero acknowledges two types of updates (or better said: 2 types of new versions): either a major update or a minor update.
A Major update
When the asset has undergone significant or structural revisions, we speak of a major update. Examples of major updates could be:
An updated visual design / layout
Replaced or added large amounts of copy
Added new chapters or significantly changed the messaging on existing copy
Revisited all the photography
etc.
A Minor update
When the asset has only undergone minor adjustments, we speak of 'minor update'. Examples of minor updates could be:
Spelling mistakes were corrected
A telephone number, or a web address was changed
A title was rephrased
A photograph was replaced
etc.