Skip to main content
Auto-generated content — pending SME review

This content was auto-generated from Fusion SMB documentation and is pending SME review. Please verify accuracy before using in partner-facing contexts.

Release Management

Understanding Fusion SMB's release cycle and support policy is essential for advising customers on upgrades and ensuring they run supported versions. This page covers version numbering, release types, and the support lifecycle.

Version Numbering

Fusion SMB uses the version format X.Y.Z:

ComponentMeaningExample
XRelease year + 10003025 = year 2025
YStable release month10 = October, 4 = April
ZMaintenance release number0 = initial, 1 = first maintenance

Example: Version 3025.10.1 is the first maintenance release of the October 2025 stable line.

Release Types

Major Releases

Major releases introduce new features and improvements. They are published twice per year, targeting:

  • Q2 — end of April (±~2 weeks)
  • Q4 — end of October (±~2 weeks)

These are referred to by their quarter: 25Q4, 26Q2, etc.

Maintenance Releases

Maintenance releases deliver bug fixes only on top of an existing stable line. They are issued every 2–3 months for each active stable line and include:

  • 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.

Support Policy: n-2 Rule

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.

When a new major release becomes available, the oldest of the three supported lines moves to End of Life.

Currently Supported Versions

VersionTypeRelease DateStatus
3026.4.0MajorPlanned ~Apr 2026Latest stable
3025.10.1Maintenance2026-03-06Supported
3025.10.0Major2025-11-10Supported
3025.4.1Maintenance2025-05-28Supported
3025.4.0Major2025-05-23Supported

Upcoming

3026.10 is planned for October 2026. When it becomes available, 3025.4.x will move to End of Life.

End of Life Versions

VersionStatus
3024.10.1End of Life
3024.10.0End of Life
3024.3.22End of Life

Versions that have reached End of Life no longer receive maintenance releases and are not eligible for official support cases.

Support Guidance for Partners

When a Customer Runs an EOL Version

  1. Inform the customer that their version is no longer supported and does not receive security or bug fixes.
  2. Recommend upgrading to the latest supported stable release (currently 3026.4).
  3. Offer assistance — Tuxera's Enterprise support team can help with upgrade planning. Direct them to Contacting Support.

When a Customer Asks About Upgrade Timing

  • Maintenance releases are safe to apply — they contain only bug fixes with no feature changes.
  • Major releases should be tested in a non-production environment first, especially if the customer uses advanced features (clustering, audit logging, custom ACL mappings).
  • Skipping versions is supported — customers can upgrade directly from any version to the latest stable release. Refer to the upgrade documentation for guidance on migrating between major versions.

Version Checks During Support Cases

Always verify the customer's version early in the support process:

tsmb-server -v

If the version is EOL, note this in the support case. While Tuxera may still provide guidance, the recommended path is an upgrade to a supported version before deep troubleshooting.

Release Cadence Summary

QuarterEvent
Q1 (Jan–Mar)Maintenance releases for active stable lines
Q2 (Apr)Major release + oldest stable line moves to EOL
Q3 (Jul–Sep)Maintenance releases for active stable lines
Q4 (Oct)Major release + oldest stable line moves to EOL

Reference: For the complete version history and lifecycle details, see Version Lifecycle & Support Policy on docs.tuxera.com.

Knowledge Check
1. What does version number 3025.10.1 mean?
2. Under the n-2 support policy, how many stable lines are simultaneously supported?
3. What should you recommend when a customer runs an End of Life version?