Versioning Scheme

Fluid follows Semantic Versioning 2.0.0

Summary

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards-compatible manner, and
3. PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Versioning Scheme - 1.5.x and earlier

Fluid uses a 4 component versioning system (e.g. 1.2.3.4)

The number in the first position (1.2.3.4) indicates a major release.

The number in the second position (1.2.3.4) indicates a minor release.

The number in the third position (1.2.3.4) indicates a bug fix release.

The number in the fourth position (1.2.3.4) indicates a special micro release.

Please note, for brevity, trailing 0's may be omitted. (1.2.0.0 === 1.2)

Major Release

• New Features
• Bug Fixes
• May not be backwards compatible
• New namespace (e.g. fluid_1_0)
  • See Versioning the Fluid Framework

Minor Release

• New Features
• Bug Fixes
• Backwards Compatible
• New namespace (e.g. fluid_1_2)
  • See Versioning the Fluid Framework

Bug Fix Release

• Bug Fixes
• Backwards Compatible
• May include small new features
• Retains current namespace

Special Micro Release

• No changes to released code
  • Usually reserved for changes to things such as build scripts