Community Edition Release Strategy

To our valued Liferay Open Source Community,

Over the past two years, Liferay has implemented significant changes to our product release strategy. These adjustments, moving from a weekly to a quarterly release cycle and introducing Long-Term Support (LTS) versions every four releases, were made to enhance the quality and reliability of our commercial offerings.

Throughout this evolution, we've also been mindful of the evolving needs of our community. In order to best support you, Liferay Portal Community Edition (CE) will now follow an annual release cycle, directly aligned with the Long-Term Support (LTS) versions of Liferay Digital Experience Platform.

We understand this is a substantial change, but we feel it’s the best way to support organizations using CE in production, even those with no interest in ever having a commercial relationship with Liferay. LTS releases are our most hardened, stable releases—the ones for which we offer a combined five years of premium and limited support—and the ones we encourage customers to use. By aligning to the LTS releases, organizations using CE in production can rest assured that they’re using only rigorously tested, enterprise-grade functionality.

One of the biggest advantages of Liferay is its flexibility to meet the needs of diverse organizations. The new CE release cycle will continue to support that. We encourage you to leverage Liferay Client Extensions and the built-in low-code tooling in CE to customize and extend Liferay to meet your unique needs.

Rest assured that you will also not have to wait for an annual LTS release in order to test new features. At Liferay we pride ourselves on continuous innovation and encourage you to experiment with the features we develop in-between LTS releases by downloading the source code that’s always available in the master branch.

We’re also evaluating ways to specifically support CE users, including offering hosting for CE deployments and access to our managed Security Plus offering, which includes machine learning-based DDoS protection, blocking bots, vulnerability reports, and auto-scaling insurance.

Have feedback? We’d love to hear from you! Please continue to engage with us by participating in our Community Slack, reading or contributing a community blog post, or joining a Liferay User Group.

We deeply appreciate your continued engagement and contributions to the Liferay ecosystem. Your passion is what makes our community so vibrant and our software so powerful. We look forward to continuing this journey together.

Sincerely,

Marco Leo
Chief Product Officer

Blogs

Every 3 months, I test the new quaterly release on my own private liferay project before doing the upgrade on my client liferay DXP. 

Now I have to wait 12 months to test the new liferay release... liferay go back in the past... in the past when a first release were done, a lot of bugs were found and we have to wait 12 months to have a new release.... with new bugs... 😩

Not a good news for us !

You should never have gotten into the habit of testing using CE before applying update to a DXP project. They have always been slightly different.

The proper way to handle updates in your DXP environ is to have your different environments running DXP (DEV, TEST, UAT and PROD) and apply the DXP quarterly release to the lower lanes and testing, then promote when they pass or make whatever adjustments to your customizations that are necessary.

For your personal project, you are free to clone the repo and do a build at any time to test the upgrade. You can fix bugs by finding the LPS tickets in JIRA and use the Git commit hashes to cherry pick and patch your CE environment. The only thing that is changing is Liferay releasing a pre-built version, otherwise you can continue to use CE in the same ways as you historically have.