iVer

iVer is a standardisation system for project versioning and abbreviations.

Versioning Format

Format: v0.0.0.0 mkn
First Number: Features and/or security updates that do not change the core structure.
Second Number: Stability updates and improvements to the existing code base.
Third Number: Design changes.
Forth Number: Minor adjustments that don't have to be visible to the end user.

Note: The number that's ahead resets the number that follows it. If you have, for example, version 1.2.3 and you make a stability update, the new version should be 1.3.0 and not 1.3.3.

Abbreviations Dex

iVer = Info Version
mk = Mark
v = Version
n = (placeholder for) Number

Use Cases

mkn:

• Shall be used when an existing project is redesigned and built from scratch but relies on the concept and developments previously achieved.
• When a new mk is launched, the versioning shall start from 1.0.0.
  

build:

• Developer side only.
• Any changes that are meant to better organise or structure the app, with 0 impact on the user end, shall be recorded with a build number.
• Changes that are build exclusive should not be included into a new release.
• Use cases include changing the name of a <div> or formatting the code differently.

Usage

Every change made to the iVer document is creating a unique concept. One mk could be entirely different from the other ones and so, on a project, it can be mentioned that it is following the "iVer versioning format mkn" to be specific or "iVer versioning format" to always refer to the latest version.

Examples:

Code:

**This repository follows the [iVer](https://github.com/frontfacer/iVer) versioning format.*

Output:

*This repository follows the iVer versioning format.

Code:

**This repository follows the [iVer](https://github.com/frontfacer/iVer) versioning format mkn.*

Output:

*This repository follows the iVer versioning format mkn.

© 2022 - 2024 | FRONTFACER
www.frontfacer.com