Asset version formatting

As users submit, update, or duplicate assets in the repository, assets are assigned version numbers that are based on the rules of the product.

Purpose

The application manages the relationship between the versions of an asset. Use the following version format and strategy to create relationships between assets and to add information about those relationships to the metadata for the asset.

Format

Use the following version rules and format when submitting assets to the repository.

You can use the format A.B.C, where A, B, and C are integers, such as "7.1.0". The asset versions are compared to each other numerically. The following list shows how asset versions are compared:
  • Newest
    • 7.2.0
    • 7.1.1
    • 7.1.0
  • Oldest
Note: You can use an infinite number of dot levels, for example, 7.0.0.0.1.1

You can also append text that acts as -1 in the integers' place; however, you must create intuitive text strings to communicate the correct version order. For example, "7.1.0" precedes version "7.1 Milestone," which precedes version "7.2." Sometimes assets will have the same version number, but one of the assets will also have text in its version number. These assets will be the same numerically, but will have different text strings. The following example illustrates how these different strings work together. The versions in the diagram below are listed from oldest at the top to newest at the bottom.


Feedback