Release support and life cycle
This page details Magnolia’s support policies and life cycles for both client-hosted and DX cloud deployments. It covers release schedules, support procedures, end-of-life policies, and migration guidance. This guidance is relevant for DX Core customers and Community Edition customers transitioning to DX Core.
Release support
All releases follow the same support life cycle as described in the Release support life cycle section.
When a new major release becomes available, the previous release continues to receive support according to the standard life cycle timeline.
Client-hosted release support policy
Magnolia will provide product updates in source and binary form for the current major version of its software several times per year. These product updates for the current major version are available for the Community Edition as well as Magnolia DX Core.
Product updates 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 product updates for the Community Edition of previous major versions.
DX Cloud release support policy
Magnolia Cloud follows the same support life cycle and support procedures as client-hosted deployments. Product updates for the current major version are made available to Magnolia Cloud customers shortly after they have been published for the client-hosted edition.
The support procedures, definitions, and release notes process described in the Client-hosted release support policy section apply equally to Cloud deployments.
Release support life cycle
This section provides an overview of Magnolia’s release support life cycle, showing which versions are currently maintained or have reached end-of-life, and which support features are available at each life cycle phase.
Actively supported product updates
We offer active support until the date specified for each release in the table below. In addition, we incorporate security fixes for a release for another year beyond the active support window.
| Release | Release date | Active support until | Limited support until (EoL) |
|---|---|---|---|
TBD |
October 2027 |
October 2028 * |
|
September 4, 2024 |
September 2026 |
September 2027 * |
|
March 27, 2020 |
September 2026 |
September 2027 * |
* To inquire about extended support for your EoL version of Magnolia, contact info@magnolia-cms.com. Support for EoL instances is provided only under special terms agreed with the client.
Retired releases
| Release | Release date | End of life |
|---|---|---|
Magnolia |
2019-06-26 |
2021-03-31 |
Magnolia |
2018-11-30 |
2019-06-26 |
Magnolia |
2018-06-25 |
2023-12-31 |
Magnolia |
2017-11-17 |
2020-06-25 |
Magnolia |
2016-11-15 |
2019-11-15 |
Magnolia |
2015-07-03 |
2018-11-15 |
Magnolia |
2014-06-23 |
2017-06-30 |
Magnolia |
2013-11-22 |
2016-06-30 |
Magnolia |
2012-03-13 |
2016-06-30 |
Magnolia |
2010-11-30 |
2015-06-30 |
Release life cycle phases
-
Beta
This initial stage of a release is primarily for partners and may still undergo changes.
-
Release candidate (RC)
A more mature release, the RC is not expected to have further changes. It is typically available for 2-3 weeks before becoming generally available.
-
General availability (GA)
A GA software release means the product is thoroughly tested, is feature-complete, and officially released to the public for production environments. It is stable, documented, and supported, moving from release candidate to unrestricted availability.
-
Active support
This phase corresponds to the first two years of the support life cycle, during which release support is provided for bug and security fixes. During this phase:
-
We don’t add new features to the release.
-
We do provide support, bug fixes and security fixes.
-
Access to artifacts (bundles, webapps, modules) in release life cycle requires a DX Core license.
-
-
Limited support
This is the third year of the support life cycle, in which only security fixes are provided.
-
End-of-life (EoL)
When the supported life of a version ends, we announce end-of-life (EoL) on this page. We do not provide formal support, bug fixes or security fixes for customers using an EoL version of Magnolia. However, we do our best to assist customers who encounter issues with EoL versions of Magnolia. DX Core customers who run an EoL version can use their support contract to verify issues, ask questions about the product, and get help with migration to a newer, supported version of the product.
Enterprise customers with a valid support contract can still use Magnolia support for questions and issues related to EoL versions.
End-of-life announcements:
-
Magnolia
6.1reached end-of-life (EoL) on March 31, 2021. The 6.1 branch is no longer maintained. -
Magnolia
6.0reached end-of-life (EoL) on June 26, 2019. The 6.0 branch is no longer maintained. -
Magnolia
5.7reached end-of-life (EoL) on December 31, 2023. The 5.7 branch is no longer maintained. -
Magnolia
5.6reached end-of-life (EoL) on June 25, 2020. The 5.6 branch is no longer maintained. -
Magnolia
5.5reached end-of-life (EoL) on November 15, 2019. The 5.5 branch is no longer maintained. -
Magnolia
5.4reached end-of-life (EoL) on November 15, 2018. The 5.4 branch is no longer maintained. -
Magnolia
4.5reached end-of-life (EoL) on June 30, 2016. The 4.5 branch is no longer maintained.Versions earlier than those listed above are also in end-of-life status.
We encourage you to upgrade your sites to the latest release of the latest Magnolia branch.
-
What type of support is there in each phase?
| Release support phase | New features | Support | Bug fixes | Security fixes |
|---|---|---|---|---|
Next major release |
Yes |
Yes |
Yes |
Yes |
Active support |
No |
Yes |
Yes |
Yes |
Limited support |
No |
Yes |
No |
Yes |
EoL |
No |
Yes* |
No |
Yes |
EEoL |
No |
Yes* |
No |
Yes |
* Support on a best effort basis to facilitate migration to supported releases.
Get help and next steps
Raising issues for supported versions
You can raise issues for supported versions of Magnolia at https://magnolia-cms.atlassian.net/jira/. Getting a fix may require upgrading to a version that includes the fix. Critical security fixes are backported to currently supported versions.
Upgrading to a supported version
Magnolia International provides assistance upgrading your EoL version to a supported version. Contact info@magnolia-cms.com to get help. Our experienced Services team will help manage and implement a smooth migration.