Version Lifecycle & Support Policy
This page describes how Fusion SMB releases are versioned, how long each release is supported, and which versions are currently active.
Release Types
Major Releases
A major release introduces new features and improvements. Major releases are published twice per year, in Q2 and Q4. These releases are referred to as YYQ2 and YYQ4, e.g., 25Q4, 26Q2 ...
The YYQ shorthand identifies the quarter a major release belongs to; the full version number is recorded in the Version Status table. For example, the 25Q4 release is 3025.10.0 and the 26Q2 release is 3026.4.0.
Maintenance Releases
A maintenance release delivers bug fixes on top of an existing stable line. Maintenance releases are issued every 2–3 months for each active stable line. They are strictly bug-fix-only in scope:
- Crash fixes
- Behavioral bug corrections
- Interoperability issues
A maintenance release may be skipped if no qualifying bugs have been identified. The maintenance process is reviewed every two months regardless of whether a release is made.
Example: 3025.4.1 is the first maintenance release on top of the 25Q2 stable release 3025.4.0.
Hotfix Releases
A hotfix release addresses zero-day vulnerabilities and other high-profile, high-severity issues that cannot wait for the regular maintenance cycle. Like a maintenance release, a hotfix contains only bug, crash, and interoperability fixes and never new features.
The difference is timing i.e., a hotfix is issued as soon as the fix is validated, rather than on the usual 2–3 month maintenance cadence. It follows the same release, signing, and verification process as a normal maintenance release but only the schedule is accelerated.
Hotfixes are delivered to every currently supported line under the n-2 support policy.
Support Policy
Fusion SMB follows an n-2 support policy: the three most recently released stable lines are simultaneously supported. Each supported stable line receives ongoing maintenance releases as described above.
The n-2 rule is the governing criterion. If an earlier time-based guideline (such as an 18-month window) conflicts with the n-2 count, the n-2 count takes precedence.
When a new major release becomes available, the oldest of the three supported lines moves to End of Life.
- 3026.4.0 — latest stable
- 3025.10.0
- 3025.4.0
3026.10.0 is planned for Q4 2026. When it becomes available, 3025.4.0 will move to End of Life.
Version Status
| Version | Type | Release Date | Status |
|---|---|---|---|
| 3026.10.0 | Major | Planned Q4 2026 | Upcoming |
| 3026.4.0 | Major | 2026-05-22 | Supported |
| 3025.10.1 | Maintenance | 2026-03-06 | Supported |
| 3025.10.0 | Major | 2025-11-10 | Supported |
| 3025.4.1 | Maintenance | 2025-05-28 | Supported |
| 3025.4.0 | Major | 2025-05-23 | Supported |
| 3024.10.1 | Maintenance | 2025-02-20 | End of Life |
| 3024.10.0 | Major | 2024-11-08 | End of Life |
| 3024.3.22 | Major | 2024-03-26 | End of Life |
End of Life
Versions that have reached End of Life (EOL) no longer receive maintenance releases and are not eligible for official support cases.
If you are running an EOL version, we recommend upgrading to 3026.4.0, the latest supported stable release. Refer to the upgrade documentation for guidance on migrating between major versions.
Our Enterprise support team is available to assist you upgrading to a supported version, do not hesitate to contact us.