The following timeline outlines how long different versions of Silverstripe CMS will remain supported, based on our Release Process.
This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.
* Subsequent releases may be created to facilitate security and critical fixes. Refer to the version End of Life table
¹ New features, APIs and enhancements to be applied in the next release
² Non-critical bugfixes and all security fixes
³ Critical bugfixes and critical security fixes
END OF LIFE
|3.5||---||Dec 31 2018||Dec 31 2018|
|3.6||---||Dec 31 2019||Dec 31 2019|
|3.7*||Apr 30 2018||Ongoing||TBC|
|3.x||Apr 30 2018||Sep 30 2021||Sep 30 2021|
|4.0||Mar 31 2018||Mar 31 2019||Mar 31 2019|
|4.1||Jun 11 2018||Mar 31 2019||Mar 31 2019|
|4.2||Dec 11 2018||Jun 30 2019||Jun 30 2019|
|4.3||Jun 30 2019||Dec 31 2019||Dec 31 2019|
|4.4||Dec 31 2019||Jun 30 2020||Jun 30 2020|
|4.5||Jul 14 2020||Jan 31 2021||Jan 31 2021|
For major releases that are in "Active development" or "Full support", minor versions are released approximately every three months, and their End-of-Life (EOL) is announced at least six months in advance. The latest minor release is supported as long as its underlying major release.
Bug and security fixes are managed differently depending on whether the underlying major release is in “Full support” or “Limited support”. For more information, read our Release Process.
Silverstripe CMS 3.2 onward, follows Semantic Versioning, which makes minor release upgrades (e.g. from 4.1 to 4.2) as painless as possible.
Silverstripe CMS 3.2 and onward, we support major versions for longer periods of time, with regular minor version releases that are supported for shorter periods.