Sulu’s direction: How we plan for the future

We’re continually improving Sulu CMS. We care about maintaining the latest technologies and are committed to a consistent, time-based release process. We aspire to keep Sulu’s feature set as streamlined as possible, while being guided by users’ needs.

We keep the Sulu Core compact and flexible.
Sulu cares about innovating. We listen to our community and add widely requested features to the Core, but keep it tight so it’s not overloaded. We usually prefer to provide additional features in separate bundles to keep the Core clean.
We minimize legacy code and technical debt.
We update Sulu to be compatible with the latest versions of its underlying technology. Sometimes we’ll break things in major versions (and let you know). We view breaking changes as a positive: they allow us to move and evolve with technology.
We’re building a stable, high-quality experience for both Developers and Content Managers.
The Sulu UI is built exclusively for Content Managers. Developers manage the web project and install new bundles. We recognize that organizations like having the freedom to use the Symfony framework to build on their requirements, unrestricted by their CMS.

Long Term Support
The Long Term Support (LTS) versions will receive fixes for security issues and critical bugs. The LTS version is the last minor version of the previous major version.
Version maintenance
Maintained versions are actively kept up and will receive bug fixes and improvements. The maintained versions of Sulu are the last two minor versions of the current major version. Support for unmaintained versions is available for a fee on request.
PHP & Symfony Compatibility
We aspire for compatibility with new PHP and Symfony versions as soon as possible. If new versions of PHP or Symfony force us to break backward compatibility in a patch version, we will establish compatibility in the next minor version.