Versionversion

Versionversion is a term used in software development to describe a meta-versioning approach in which multiple layers of version information are tracked for a single artifact. The term repeats the word version to emphasize that both the artifact and the system that labels it can be versioned. In practice, versionversion refers to separating the version of the product from the versioning metadata that governs how versions are assigned and evolved over time.

Conceptually, versionversion encompasses two ideas. First, it involves maintaining a history of the versioning policy itself, sometimes called policy versions. Second, it encodes that history alongside the artifact’s own version in a composite identifier. This separation can improve traceability, reproducibility, and governance within complex release pipelines.

Notation examples commonly cited in discussions include augmenting a semantic version with build metadata that carries a version number for the versioning policy. For instance, a release labeled 2.1.0+vv2 would indicate product version 2.1.0 and versioning policy version 2. More explicit implementations may use a separate metadata history repository or file to record the sequence of policy versions and their impact on releases.

Usage and reception of versionversion are mainly found in engineering blogs and informal forums as a way to address governance in large projects. It is not widely standardized, so practitioners should document conventions clearly to avoid confusion. The approach is meant to complement established practices such as semantic versioning, build metadata, and provenance tracking, rather than replace them.

See also semantic versioning, build metadata, provenance, release governance.