Magnolia maintenance policy
This page contains the Magnolia CMS maintenance policy as well as information on the frequency of releases and updates.
Magnolia Client-Hosted release policy
Magnolia will make maintenance releases in source and binary form for the current major version of its software several times per year. Maintenance releases for the current major version are available for the Community Edition as well as Magnolia DX Core.
Maintenance releases for previous major versions of Magnolia are available to Magnolia DX Core customers only (i.e. customers that have an active subscription to Magnolia DX Core). We don’t make maintenance releases to the Community Edition of previous major versions.
Magnolia classifies major releases (x.y
) into Long-Term Support (LTS) and Feature releases.
Long-term support (LTS)
Unless otherwise stated, Long-term support (LTS) releases are maintained for at least two years after their release. When a new major release is made available, the current LTS release goes into maintenance mode.
The duration of maintenance mode is determined by Magnolia. |
Feature releases
Feature releases are fully maintained until the following LTS or Feature release is available.
When a new LTS or Feature release is available, we will ship one more maintenance release after which the current Feature release can be declared end-of-life:
-
Immediately with the final maintenance release.
-
After an extended end-of-life period, to support migration.
Magnolia Cloud maintenance release policy
Magnolia will make maintenance releases in source and binary form for the current major version of its software several times per year. These releases will be available to Magnolia Cloud customers shortly after they have been published for the client-hosted edition.