Skip to content

Latest commit

 

History

History
32 lines (26 loc) · 1.46 KB

versioning.md

File metadata and controls

32 lines (26 loc) · 1.46 KB
Raw

Versioning Strategy

Version Format

The Broker version is stored in the broker's RPM spec file, ansible-service-broker.spec, and is in the form of MAJOR.MINOR.PATCH incremented by the following rules:

  • MAJOR version when incompatible API changes are made.
  • MINOR version when a new version of openshift/origin is being targeted.
  • PATCH version when tagged via tito tag.

NOTE: The first official release of the broker, 1.0.x, targeted OpenShift Origin release v3.7.0. Following the versioning rules, the version was bumped to 1.1.x for OpenShift Origin release v3.9.0 and again to 1.2.x for OpenShift Origin release v3.10.0.

Branching and Tagging

All development work is done on the master branch. New branches are created when a submitted Pull Request is targeting a future release. This is done to allow Pull Requests to move forward when new features are no longer being added to the currently targeted OpenShift releases. When a new branch is created, it will be named release-MAJOR.MINOR and the version in the master branch will be bumped based on the rules in Version Format.