Skip to content

Product Release Lifecycle

This document outlines the release lifecycle and version management policies for Yellowbrick Data Warehouse releases.

Overview

Yellowbrick follows a semantic versioning system (MAJOR.MINOR.MICRO). Each release level has a strictly defined support window to ensure stability and predictability for platform upgrades.

Support Policy Definition

Release TypeFormatSupport DurationDescription
Major7.x.x24 MonthsSignificant architectural changes. Sets the foundation for subsequent releases.
Minor7.X.x6 MonthsFeature enhancements. Follows an upgrade-only path (e.g., 7.2 → 7.3) and extends Major support duration.
Micro7.x.XInheritedBug fixes and security patches. Inherits the End of Life (EOL) date of the parent Minor version.

Release Calendar

The following table lists the current and recent versions of Yellowbrick, their alignment with Kubernetes versions, and their support status.

VersionKubernetes VersionRelease DateEnd of SupportStatus
7.41.32Dec 4, 2025May 5, 2026Current
7.31.31 / 1.32Jul 25, 2025Jan 25, 2026Active
7.21.30Apr 29, 2025Oct 29, 2025End of Life
7.11.30Jan 24, 2025Jul 24, 2025End of Life

Note: Micro releases (e.g., 7.3.1) are not listed in the main calendar as they share the "End of Support" date of their minor version.

Micro Version Detail

Micro versions provide critical fixes. They do not extend the support window of the Minor version. Latest micro per minor listed below:

Minor VersionMicroRelease DateSupport Ends
7.37.3.2Nov 06, 2025Jan 25, 2026
7.27.2.3Jun 13, 2025Oct 29, 2025
7.17.1.3Feb 24, 2025Jul 24, 2025

Best Practices

  1. Upgrade Planning: Plan upgrades at least 30 days before a Minor version's End of Life date.
  2. Forward Compatibility: Upgrades (e.g., 7.2 to 7.3) preserve compatibility, any changes in behavior are documented here. Downgrades are not supported for Minor versions.
  3. Environment Testing: Validate new versions in a non-production environment before applying to production.