Just came across the news that Liferay Community Edition (CE) will now have one release per year, and it really got me thinking.
On one hand, that sounds great — fewer upgrades, more time for stability, and maybe less hassle dealing with frequent version changes. But on the flip side, it also means new features and improvements might take longer to reach the community.
we’ve been strong advocates of using Liferay CE to build cost-effective, scalable solutions — especially for startups and small businesses that don’t necessarily need the full DXP stack. But now, with this new release cycle, we’re wondering if it’s still the best long-term approach for client projects.
Curious to know what others think —
Will this new release model change how you use CE?
Do you still see it as production-ready for client work?
For some extra information regarding the updated CE Release Cycle, I recommend checking Marco Leo’s Blog Post on the topic.
I believe this strategy aligns very well with your goals, and if there is a relevant new feature that you want to use before it becomes available in the community edition, it is always possible to build from source.
My main concern is that it is not just updates that will wait a year, but I believe that critical security issues will also not be fixed for up to a year… Please correct me if I am wrong, but this is how I understand it.
So it sort of makes it something you don’t really want running live on the internet… maybe on an intranet behind a firewall, and just for testing stuff out, but for the anything running on the internet, unfortunately I must admit I am starting to think about looking elsewhere…