We're pleased to announce SilverStripe 2.4.2, our second update to the 2.4 codebase. This is now our recommended version of SilverStripe CMS to use on production websites.
As always, we'd like to thank members of our community for helping out with this release, by contributing patches, filing bugs, and generally sticking around to help others - you guys rock!
We're pleased to announce 2.4.1, our first update to the 2.4 codebase. You can check a full list of changes in our changelog, but here are some highlights:
Mostly, however, 2.4.1 is a security release for vulnerabilities discovered recently and contains all enhancements and bugfixes since the 2.4.0 release.
We're excited to tell you that we just released SilverStripe version 2.4! This is a major new release and an important milestone for the SilverStripe community, the open source project, and our company.
SilverStripe 2.4 is the culmination of over a year's worth of development. We fixed 391 tickets and had over 1,400 changelog entries. A large number of the patches that went into 2.4 have come from you, the community, and we're especially happy that there's been increasing community involvement.
We're excited to say we're extremely close to releasing a stable version of SilverStripe 2.4.
A month ago we released Release Candidate 1. Thanks to community feedback and continued testing, we're issuing an update today, SilverStripe 2.4 Release Candidate 2. A huge thank you to everyone who has taken the time to download and test this release and file bug reports.
Today we've moved significantly closer to a final and stable version of SilverStripe v2.4. You can now download SilverStripe v2.4 Release Candidate 1, which fixes bugs and incorporates feedback from the community since our Beta releases.
We'd appreciate you testing this release, and seeing whether your existing sites upgrade smoothly to this version.Version 2.4 does represent a major version update, providing a number of new features needed to run larger and more complex websites. Whether you're needing to run on SilverStripe on another database, make use of nested URLs, or keen to take advantage of improved performance or wider unit-test coverage, there's something in this release that will help everyone who uses SilverStripe.
Now that we've reached Release Candidate 1, the features in SilverStripe 2.4 are finalised. We have described the major features in earlier posts, but you can look forward to hearing about them in much more depth as we head towards the final release.
We're extremely excited to announce SilverStripe v2.4 is now at beta release stage!
This means it's ready for testing by our community. We've made a number of changes since the 2.4 alpha release in November, and we're continuing to polish the intended features in preparation for the stable version. We do not recommend using this version of SilverStripe for production sites yet unless extensive testing is done.
Yesterday we released an update to the SilverStripe CMS. As it fixes security vulnerabilities in our software, we recommend that production websites should upgrade to this version.
No API changes are generated in this release, so existing modules and websites should upgrade easily. Related to this release, we also issued a security update for the SilverStripe forum module.
SilverStripe v2.3.4 has just been released! This is now the best version of our software to use. This version solves a number of bugs, some of which relate to security vulnerabilities. Thanks go to community members who identified bugs and contributed fixes to them!
We're extremely excited to announce SilverStripe v2.4 is now at alpha release stage!
This means it's ready for testing by our community while we continue to complete the intended features for the stable version, and complete our own testing. We do not recommend using this version of SilverStripe for production sites yet, unless you perform extensive testing on your own site first.
SilverStripe v2.3.3 has just been released! This is now the best version of our software to use. This version solves a number of bugs both at the code level for those working with Sapphire, and solves a few CMS interface bugs.
A big round of thanks go to community members who identified bugs and contributed fixes to them!