Unified Release and Versioning Model: What It Means for You

Greater predictability, clearer planning, and a consistent experience across all Matrix42 solutions

Last year, we introduced a unified, tiered release and versioning model across the Matrix42 portfolio. The goal was simple: to make it easier for our customers and partners to plan, adopt innovations, and stay supported — without complexity.

Here’s a clear overview of how the unified release and versioning model works and what to expect from upcoming releases.

Why a Unified Release Model?

With a growing and evolving portfolio, a unified release and versioning model brings consistency across all Matrix42 solutions. Instead of different schedules and structures per product, customers now benefit from:

• A synchronized release rhythm
• A clear distinction between major, minor, and service releases
• Simpler planning and upgrade decisions
• Streamlined support and communication

This approach ensures transparency, predictability, and earlier access to innovation — across the entire Matrix42 ecosystem.

The Three Release Tiers Explained

Our unified model is based on three clearly defined release types:

1. Major Releases

• Delivered twice per year
• Introduce significant new features, innovations, and platform-wide improvements
• Mandatory for all customers
• Define the supported baseline for fixes and enhancements
• Upcoming Major Releases:
• End of April 2026
• End of October 2026
• For cloud customers, deployment is performed automatically
• For on-premises customers, upgrading to the latest major release is required to maintain support

2. Minor Releases

• Delivered as needed, depending on the product

• Include enhancements, functional improvements, and cumulative updates

• Build on the most recent major release

3. Service Releases

• Delivered monthly or on demand

• Focus on:

  • Bug fixes
  • Security patches
  • Performance and stability improvements

What This Means for Customers and Partners

The unified release and versioning model is designed to simplify your day-to-day operations and long-term planning:

• Better predictability and planning

Plan upgrades and internal resources with confidence.

• Earlier access to innovation

New capabilities are delivered in structured, predictable cycles.

• Simplified support

A unified versioning structure reduces complexity across environments.

• Clear communication and enablement

Updates, documentation, and enablement materials are aligned with each release type.

Supported Release Versions Policy (Effective January 1, 2026)

To further improve clarity and consistency, the Supported Release Versions Policy comes into effect on January 1, 2026.

Under this policy:

• Each major release is supported for 12 months
• Fixes and updates are delivered until the next major release (typically after six months)
• After a new major release becomes available:

o   Fixes are provided only for the latest version

o   Older major releases continue to receive standard support until their end of support (EOS)

Example: Enterprise ITSM Versioning Transition

To illustrate how the model works in practice:

• The first Major Release under the new, v25.4, replaced Matrix42 Enterprise ITSM v12.1.3
• The next Major Release, v26.1, is scheduled for end of April
• End of Support for v25.4 is 12 months after its release

Fix policy:

• Fixes released before the next major release apply to the current version
• Fixes released after the next major release are available only for the latest version and later

Important Note for Long Term Business Support Customers

If you are a Long-Term Business Support (LTBS) customer, your existing agreement remains unchanged and is not affected by the new Supported Release Versions Policy.

In Summary

The unified release and versioning model provides a clear, predictable, and consistent framework for all Matrix42 customers. It simplifies planning, accelerates innovation adoption, and ensures transparency across the entire product portfolio. Stay tuned for further updates on enablement resources, early access programs, and product-specific milestones.