Skip to main content
koolishami
Staff
koolishami
Staff
March 16, 2026

Technical Tip: Understanding software release cycles and choosing the optimal version

  • March 16, 2026
  • 0 replies
  • 233 views
Description

This article provides a generalized framework for choosing between 'Mature' (Maintenance) and 'Feature' (New) releases.

 

Selecting the appropriate software version for an enterprise environment requires balancing the need for system stability against the requirement for new features. Fortinet products typically follow a release numbering convention that indicates the maturity of the firmware.
Scope FortiSIEM.
Solution

When reviewing release notes, versions generally fall into three categories based on their position in the software lifecycle:

  1. The maintenance release (e.g., v7.3.5).

  • Characteristics: High patch count (e.g., the '.5' in v7.3.5).

  • Focus: Stability and bug fixes.

  • Best for: Production environments where uptime is the highest priority and current features meet all business requirements.

  • Trade-off: Does not include the latest feature sets found in newer major branches and may reach End of Engineering (EOE) support sooner than later branches.

 

  1. The feature release (e.g., v7.5.0).

  • Characteristics: Major or minor version increment with a low patch count (e.g., '.0').

  • Focus: New functionality, UI/UX improvements, and expanded integrations.

  • Best for: Lab environments, 'early adopter' scenarios, or environments that specifically require a new feature only available in this version.

  • Trade-off: Higher risk of encountering undocumented issues as it has not yet undergone multiple cycles of public patch refinement.

 

  1. The balanced release (e.g., v7.4.2).

  • Characteristics: Mid-tier patch count.

  • Focus: Hybrid of newer features and initial bug mitigation.

  • Best For: Organizations looking to modernize their feature set while maintaining a moderate safety margin.

  • Trade-off: Offers a middle ground but may still lack the long-term field-testing of the high-patch maintenance branch.

 

Recommendation.

Fortinet recommends reviewing the 'What's New' and 'Resolved Issues' sections of the specific Release Notes for each version before performing an upgrade.

  • For mission-critical systems, it is generally advised to stay on a branch with a higher patch version (e.g., v.4 or higher).

  • Always perform a full system backup/snapshot before any version migration/upgrade.
    Terms & ConditionsAccessibility statement