Skip to main content

Coming This March: A Simpler, More Predictable FME Release Versioning Model

  • February 12, 2026
  • 7 replies
  • 956 views
SagitAtSafe
Safer
Forum|alt.badge.img+3

Starting with FME 2026.1, we are introducing an updated release versioning approach for FME, designed to make releases easier to understand, upgrades simpler to plan, and delivery more predictable.

What’s Changing

Beginning in March 2026, FME will move to a simplified, calendar-based versioning model paired with a consistent quarterly release cadence.

A Simpler Versioning Format

FME releases will now follow this format: YYYY. Release 

This format will be used consistently across the platform, making it easier to understand when a release was delivered and how current it is.

A Predictable Quarterly Release Cadence

FME will ship four planned releases per year, on a fixed schedule:

  • .1 — March
  • .2 — June
  • .3 — September
  • .4 — December

As part of this change, the traditional “.0” release is being retired. Every quarterly release is treated as production-ready, with the same level of quality assurance and testing.

Why We’re Making This Change

This update reflects how customers use FME today and supports a more modern, continuous delivery model.

  • Clarity & Simplicity – A calendar-based versioning scheme makes it easier to understand when a release was delivered.
  • Predictable Planning – A fixed quarterly cadence helps teams plan testing, deployments, and upgrades with confidence.
  • Faster Time to Value – New features and improvements are delivered regularly throughout the year.
  • Consistent Quality Across Releases – Every quarterly release meets the same production standards.
  • Easier Adoption – A predictable rhythm reduces friction and makes it easier to stay current.

What to Expect Next

The first release under this new model, FME 2026.1, will be available in March 2026. From there, you can expect regular quarterly releases throughout the year using the same naming convention.

Join the discussion below if you have questions or feedback.

7 replies

hkingsbury
Celebrity
Forum|alt.badge.img+69
  • Celebrity
  • February 12, 2026

Is there a target day within each release month?


fornberry
Contributor
Forum|alt.badge.img+1
  • Contributor
  • February 16, 2026

Now when changing the versioning, is it correct to treat the version 2026.1 as equal to the “2025.3” (old versioning system)?

I’m thinking in the context of updating FME Flow from 2024 version directly to 2026, since the coming 2026 versions essensially are 2025 versions when using the old version system.


hkingsbury
Celebrity
Forum|alt.badge.img+69
  • Celebrity
  • February 16, 2026

Now when changing the versioning, is it correct to treat the version 2026.1 as equal to the “2025.3” (old versioning system)?

I’m thinking in the context of updating FME Flow from 2024 version directly to 2026, since the coming 2026 versions essensially are 2025 versions when using the old version system.

2026.1 is the first release of 2026

Instead of starting at xxxx.0, it starts at xxxx.1

 

If i understand correctly, in the previous version naming convention .x releases where ‘significant’ updates to the underlying year. That’s why you’d see 2025.3 released in 2026.

Now Safe are doing a quarterly release regardless of any ‘significant’ improvements. This provides a more structured and reliable cadence 


SagitAtSafe
Safer
Forum|alt.badge.img+3
  • Author
  • Safer
  • February 17, 2026

Is there a target day within each release month?

@hkingsbury Thanks for your question! Our target timing for each quarterly release is generally the middle to later part of the release month.


rudy_v
Contributor
Forum|alt.badge.img+6
  • Contributor
  • February 17, 2026

My Question - so no more in between bug fixes - like current 2025.2.2 etc.

I would like to see - from a release, incremental updates. And also in place upgrade of FME Flow. And the current pain - Database. Upgrade option needed for Database.

Also currently the Database install are only available after you install FME Flow - like to see a download option.

Another that would be great is more administrator in the GUI - like amending config files. Stop and Start of services in one interface.

FME Flow and Form - IMO are amazing products, but I think we need more/better administrator tools/interfaces.

Rudy

 


stewartatsafe
Safer
Forum|alt.badge.img+10

My Question - so no more in between bug fixes - like current 2025.2.2 etc.

I would like to see - from a release, incremental updates. And also in place upgrade of FME Flow. And the current pain - Database. Upgrade option needed for Database.

Also currently the Database install are only available after you install FME Flow - like to see a download option.

Another that would be great is more administrator in the GUI - like amending config files. Stop and Start of services in one interface.

FME Flow and Form - IMO are amazing products, but I think we need more/better administrator tools/interfaces.

Rudy

 

Following each major release, we provide monthly updates that primarily include minor feature enhancements and bug fixes, which typically fall in the later part of the release month.  These updates follow a consistent monthly cadence outlined below:

  • 2026.2.0 (Major)
    • 2026.2.1 (Update)
    • 2026.2.2 (Update)
  • 2026.3.0 (Major)
    • 2026.3.1 (Update)
    • 2026.3.2 (Update)
  • 2026.4.0 (Major)
    • 2026.4.1 (Update)
    • 2026.4.2 (Update)

Appreciate the feedback on the better admin/upgrade workflows ​@rudy_v. This more structured release cadence—and an increased internal discipline around what goes into each release—sets us up to be able to provide incremental updates in the future. It will not be in an immediate release, but it is on our radar.


philippeb
Enthusiast
Forum|alt.badge.img+22
  • Enthusiast
  • February 26, 2026

So instead of updating to .1 we’ll update to .2. No big deal.