FMOS Release Process
Release Types
FireMon offers the following types of releases within two release tracks.
| Type | Purpose | Cadence | Name Example |
|---|---|---|---|
| Enterprise Release |
Annual “gold standard” baseline. Contains new/revised components, all features from the prior year, and maintenance fixes. |
Yearly | 2026.1 |
| Feature Release | Adds new features during the year on top of current Enterprise Release. Includes latest Enterprise maintenance fixes. | Monthly | 2026.2.0 |
| Enterprise Maintenance Release | Bug and security fixes only, no new features. Maintains backward compatibility. | Monthly | 2026.1.2 |
| Patch Release |
Urgent fixes for critical bugs and security issues. |
As needed | 2026.1.2.1 |
Enterprise Release
An Enterprise Release represents our golden standard version. It includes new or significantly revised software components, enabling support for new functionality or hardware while managing the risks of migrating from older releases to a single test cycle. It serves as a container for Feature and Maintenance Releases (e.g., 2025.1).
Feature Release
The Feature Release supports ongoing feature development within an Enterprise Release. Its aim is to introduce new features aligned with the Enterprise Release over time. It integrates new features, hardware support, and bug fixes. Multiple Feature Releases occur within each Enterprise Release, functioning as a container for Maintenance Releases (e.g., 2025.2).
Feature Releases occur monthly and include the latest maintenance release along with any newly added features.
Maintenance Release
A Maintenance Release derives from the Enterprise Release, freezing its software functionality and behavior at a specific point in time to ensure stability. It focuses on bug fixes without introducing new features, with behavior changes limited to necessary fixes. Backward compatibility is maintained (e.g., 2025.1.1).
Maintenance Releases are monthly, comprising all individual fixes tested together and released as a single patch. This release corrects security flaws or minor bugs without altering core components or adding new features. Best practices permit only fixes in a maintenance branch, prohibiting enhancements and interface changes unless absolutely necessary. The goal is to maintain product stability, as customers expect reliability.
Occasionally, with leadership approval, an important feature may be back-ported to a maintenance release, provided it does not disrupt existing functionality. All other changes must be deferred to an upcoming release in a professionally managed project.
Patch Release
Patch releases are issued as needed to address critical bugs, specifically those creating security vulnerabilities or system failures (e.g., 2026.1.1.1 or 2026.2.1.1).
Release Tracks
| Track | Audience | Cadence | Contents |
|---|---|---|---|
|
Enterprise Upgrade Release Track |
Customers prioritizing stability |
Annual Enterprise Release + Monthly Maintenance | All prior year’s features + bug & security fixes |
|
Feature Upgrade Release Track |
Customers wanting latest features | Monthly Feature Release + Maintenance | New features + bug & security fixes |
Enterprise Upgrade Release Track
-
Conducted once a year, with monthly maintenance updates.
-
It will include:
-
All content from the previous enterprise release
-
New features developed since the last enterprise release (all feature releases from the previous year)
-
All maintenance and patch releases since the last enterprise release (all maintenance and patch releases from the previous year)
-
-
The Enterprise Upgrade Release Track appeals to customers seeking stability, providing annual new content while ensuring monthly maintenance updates and patches.
Feature Upgrade Release Track
-
Conducted monthly.
-
It will include:
-
All content from the latest enterprise release (current year)
-
Content from previous feature release(s)
-
New features developed since the last feature release
-
All maintenance and patch releases since the last feature release
-
-
The Feature Upgrade Release Track attracts customers interested in the latest features while keeping up with monthly maintenance updates and patches.
Support and Lifecycle
Supported tracks: We support multiple versions concurrently, typically the latest Enterprise Release, its predecessor with security fixes, and the Feature Release track.
End of Engineering Support (EOES): After this date, we provide only critical security patches, with no new features or routine fixes for the Enterprise Release Track or Feature Release track. There is limited maintenance fixes for device packs. EOES occurs 12 months from the baseline Enterprise Release General Availability (GA).
End of Support (EOS): This marks the end of all support, including patches, 18 months from the Enterprise Release GA.
Recommended versions: For the Enterprise Upgrade Release track, FireMon recommends staying one or two maintenance releases behind the latest version for stability and advises upgrading at least quarterly to stay current. For the Feature Upgrade Release track, FireMon advises upgrading at least quarterly to stay current with new features, maintenance, and security fixes. Upgrade paths will be communicated through User Center announcements and release notes.
Release Roadmap (2026 – 2027)
The following roadmap outlines the planned Enterprise, Maintenance, and Feature releases. Enterprise releases remain supported for 12 months (GA) and reach End of Extended Support (EoES) after 18 months.
| Month | Enterprise | Maintenance | Feature | Notes |
|---|---|---|---|---|
| January | 2026.1.0 |
EoES: 12mo 1/31/2027 EOS: 18mo 7/31/2027 |
||
| February | 2026.1.1 | 2026.2.0 | ||
| March | 2026.1.2 | 2026.2.1 | ||
| April | 2025.1.3 | 2026.2.2 | ||
| May | 2026.1.4 | 2026.2.3 | ||
| June | 2026.1.5 | 2026.2.4 | ||
| July | 2026.1.6 | 2026.2.5 | ||
| August | 2026.1.7 | 2026.2.6 | ||
| September | 2026.1.8 | 2026.2.7 | ||
| October | 2026.1.9 | 2026.2.8 | ||
| November | 2026.1.10 | 2026.2.9 | ||
| December | 2026.1.11 | 2026.2.10 | ||
| January | 2027.1.0 | 2026.1.12 |
EOES: 12mo 1/31/2028 EOS: 18mo 7/31/2028 |
|
| February | 2027.1.1 | 2027.2.0 |
Naming Convention
-
Enterprise: Year.ReleaseNumber → 2026.1
-
Maintenance: EnterpriseRelease.MaintenanceNumber → 2026.1.1, 2026.1.2
-
Feature: Year.2.FeatureIncrement → 2026.2.0, 2026.2.1, 2026.2.2
-
Patch: Increment last digit of maintenance or feature version → 2026.1.2.1