YaK User Documentation
YaK Landing PageVisit dbi-services.comContact us
YaK Release 2.1
YaK Release 2.1
  • Welcome
  • Introduction
    • YaK Core
    • YaK Components
    • Terms and definitions
  • User interface
    • Dashboard
    • Infrastructures
    • Servers
    • Components
    • Jobs
    • Configuration
    • Administration
  • YaK Demo
  • Versioning & Compatibility matrix
  • Release Notes
    • YaK components types
      • PostgreSQL
      • Oracle
  • Installation
    • System requirements
    • Install YaK Core
      • Install YaK on your own K8S cluster
      • Install YaK on Rancher Desktop
      • Uninstall Yak
  • YaK step-by-step usage
  • Configuration
    • Secrets
    • Templates
    • Provider shapes
    • Provider images
    • Artifact providers
  • Manage infrastructures
    • Declare infrastructures
    • Attach Secrets
    • Detach Secrets
  • Manage Servers
    • Declare servers
      • Basics
      • Storage
      • Attach secrets
    • Edit server configuration
    • Deploy servers
    • Destroy servers
    • Delete servers
    • Start / Stop servers
  • Manage Components
    • Artifacts requirements
    • Component types
      • PostgreSQL
        • Description
        • Pre-requisites
        • Component references
          • PostgreSQL 2.0.0
            • Standalone deployment variables
            • HA deployment variables
      • Oracle
        • Description
        • Pre-requisites
        • Component references
          • Oracle 2.0.0
            • Standalone variables
  • Use cases
    • On-Premises
    • AWS
    • Azure
    • OCI
  • Appendix
    • Create SSH Keys with PuTTYgen
    • Roles
Powered by GitBook
On this page
  • Versioning
  • YaK Core
  • YaK Components
  • Compatibility matrix
  • Support policy

Versioning & Compatibility matrix

Versioning

YaK Core

YaK releases follow the Semantic Versioning scheme (SemVer), that encodes versions by a three-part version numbering (ex: YaK-A.B.C).

  • The 1st digit (A) indicates the major version of the YaK Core

  • The 2nd digit (B) indicates the minor version of the YaK Core

  • The 3rd digit (C) is reserved for future use (ex: emergency fixes, patches... of the YaK Core)

YaK Components

Each YaK Component follows the same versioning convention as the YaK Core (ex: Component-X.Y.Z)

  • The 1st digit (X) is always in-line with the YaK Core major version (A)

  • The 2nd digit (Y) indicates the major version of the YaK component itself (ex: Oracle-2.8.0)

  • The 3rd digit (Z) is reserved for minor changes or patches/fixes of the component (Oracle PSU, HF, etc...)

Compatibility matrix

Minor versions of the YaK Core/UI/CLI or of any YaK Component Types shall be cumulative. This means that any functionality or feature that worked in minor release "n" shall continue to work in the subsequent minor release "n+1".

However, this principle might not be always true for major releases as they might introduce breaking changes.

All components pertaining to the same major version should be compatible with the major core version. (ex: oracle-2.8.0 shall be compatible with all minor versions of the YaK Core 2.b.c).

Support policy

Only the latest major version of the YaK Core is supported.

A preliminary upgrade to the latest YaK Core version is mandatory to receive support from dbi services.

PreviousYaK DemoNextRelease Notes

Last updated 2 months ago