Ahead of the next Mender release (coming soon!), the Mender team announces its new product release and versioning scheme. The new Mender versioning impacts how Mender is released, supported, and versioned, aimed to deliver new Mender features faster and provide our customers and community with a more seamless experience
Historically, all components of Mender, such as the Client and Server, were released as a full bundle and denoted with an overarching version number. Components inside the bundle had their individual version numbers as well. For example, the Mender 3.7.x bundle release contained Mender Client 4.0.x.
While the historical approach has sufficed in the past, the Mender team has started to foresee some major problems with applying this approach for planned future releases.
Therefore, Mender will not be released as a bundle version going forward. Mender 3.7.x is the last bundle release of Mender.
Going forward, all Mender components will be separated, released independent of other components, and versioned individually. Today, this list includes:
As mentioned, the Mender team plans to grow the list of Mender components over time as Mender further advances and tackles even more complex use cases and environments. In many cases, some of the components will be released around the same time. But this will not always be the case, and each component will always have its own versioning.
For the next release, the following components will be released:
Apart from removing bundle release versioning, Mender will continue to follow Semantic Versioning for the components. The long-term support (LTS) policy remains unchanged, it is just applied to individual components instead of the bundle going forward. The released Mender 3.7 bundle support is unchanged (supported until May 2025).
As Mender continues to lead the industry in over-the-air (OTA) update infrastructure, this change will enable the Mender team to deliver faster improvements to all users.