Skip to main content
On this page

Releases and support

Release cadence

  • Quarterly stable releases, each based on a vetted upstream OpenTelemetry Collector release.
  • Long-term support (LTS) releases every 18 months, with extended maintenance windows for teams that upgrade less often.

Stable releases land in February, May, August, and November. The next one is expected in the next quarterly window.

Release notes and upgrade playbooks ship with each release in the Tulip repository.

Backport policy

  • Security fixes: CVEs rated Critical, High, or Medium (CVSS 7.0 and above) are backported to all supported releases.
  • Production-stability bugs: Severity 1 and selected Severity 2 issues are evaluated and backported when confirmed.
  • Critical upstream fixes: OpenTelemetry Collector fixes that affect Tulip users are backported.
  • Non-critical bugs and feature enhancements are not backported; upgrading to the latest stable release picks them up.

What support covers

  • Incident triage for bugs in supported components and versions.
  • Fixes delivered through patch releases, without disruptive upgrades.
  • Performance regression analysis when behavior deviates from release notes.
  • Security notice relay and mitigation guidance for supported components.
  • Documentation on upgrade paths and known incompatibilities.
  • Guided version transitions with migration checklists.

What support does not cover

  • Net-new feature development or upstream roadmap commitments.
  • Components outside the official manifest; those get best-effort guidance.

Two support plans are available, Standard and Enterprise. They differ in coverage hours (business hours versus around-the-clock response for critical issues), response targets, and contact channels. Current plans, response times, and pricing are on the Tulip product page.