Open Data Products Governance model
  • Governance of Open Data Product Specification
  • Community Code of Conduct
  • Contributions
    • Contributing changes
    • Contributor Agreement
  • Decision-making processes
  • Specification
    • Versioning practices
    • Breaking changes
    • Releases
  • Organization
    • Roles and responsibilities
    • Strategy Group
    • Business Advisory Group
    • Technical Steering Committee
    • Joining as organization
    • Joining as individual
  • Design
  • Finance
  • Timeline of ODPS
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Specification

Versioning practices

Last updated 1 year ago

Was this helpful?

Semver is used

ODPI uses —semantic versioning—on our components. The three types of versions are:

  • Major versions contain

  • Minor versions add new features or deprecate existing features without

  • Patch versions fix defects or optimize existing features without breaking changes.

Version numbers are presented Major.Minor.Patch, for example, 3.2.1.

Once a versioned package has been released, the contents of that version must not be modified. Any modifications must be released as a new version.

The major version must be incremented for all breaking changes.

The minor version must be incremented if:

  • New, backward-compatible functionality is introduced to the public specification.

  • Any public specification functionality is marked as deprecated

The patch version must be reset to 0 when minor version is incremented

SemVer
breaking changes.
breaking changes.