Edit on github

Datacoves versioning

Datacoves uses semantic versioning in all our docker images, and Datacoves releases.

MAJOR.MINOR.PATCH

The MAJOR.MINOR versions are defined as below and PATCH is an autogenerated (timestamp) generated when the release is built.

Our criteria

When do we bump the MAJOR version?

When we make incompatible changes or we introduce compatible changes but deprecate features:

  • Any python library upgrade (including dbt) that requires changes in the customer's analytics(dbt) git repo
  • Airbyte, Airflow, DataHub, Superset upgrades that require reconfiguration
  • Datacoves core changes that require human intervention
  • Airbyte, Airflow, DataHub, Superset that do not require reconfiguration, but several features are being deprecated

When should we bump the MINOR version?

  • When we make compatible changes, such as new features or upgrade dependencies
  • Patch version changes to dbt e.g. 1.8.3 to 1.8.5
  • Compatible updates to dbt e.g. 1.7.x to 1.8.x
  • Compatible update to Airbyte, Airflow, DataHub, Superset that do not require reconfiguration

Everything else is a PATCH

  • Bug fixes, performance enhancements

Images tags

Images are pushed with the folling tags:

  • MAJOR
  • MAJOR.MINOR
  • MAJOR.MINOR.PATCH
  • MAJOR.MINOR.PATCH-\<commit sha>

CI jobs that use Datacoves images could reference any of the above, depending on how specific the customer needs to be.