Anyone having worked in the software business is used to these kind of questions. Even if all releases are not the same, from the time we actually release it is certainly a given that it is production ready! Otherwise we would keep releasing beta...
That aside, here are my top 3 reasons why you should not hesitate to use eZ Publish 5!
- eZ Publish 5.0 is also eZ Publish 4.8!
Well I am playing with the numbers here and some might not like it - but bare with me. eZ Publish 5 brings a lot of new things into the architecture (like the adoption of the Symfony stack or the new scope complete REST API) but more than anything, we have made it “dual kernel” which means it embeds a 4.x kernel and architecture that act as a fall back. Thanks to this system, a site developed on and for the 4.x generation can fully work on 5.0 without having to upgrade the templates or database (and can still benefit from the new REST API). So if what worries you about the 5.0 release is the new “unknown” architecture, rest assured - 5.0 is above all designed to run the legacy architecture to ensure the long term transition is easy! Another perspective can, in fact, be that 5.0 is also the latest and more stable version of the 4.x series!
- eZ Publish 5.0 will be the latest stable version, as soon as it is out
No need to elaborate on this. Running beta software is certainly a risk but running on the latest stable release of a software is what people should always look for. So if you start a new project, why starting it on an older release? It reminds me of a car race where those drivers that have been penalized have to start from the stand and not from the grid - and 30 seconds after everyone else too...Of course if we are talking of existing project, there are other considerations that I will touch on at the end of this post, but surely, latest and stable also means better maintenance and better support.
- You don’t want to miss the opportunities brought by eZ Publish 5!
I won’t explore here the opportunities that eZ Publish 5.x series will offer you such as from the development consideration (for instance, embedding the best php framework available on the market and offering state of the art APIs) to production (e.g. delivering way better performance and jumping to new levels of scalability) and from the multiple business reasons (offering unequalled online marketing features for improved customer experience) to usability (on track to offer a new state of the art user interface). We must emphasize, however, that we know all this is not rolling out in one go, and so we have deliberately decided to go for a smooth and progressive transition. While as a user you take no risk since the legacy stack is all there and supported, running eZ Publish 5.0 will give you the opportunity, if you wish, to put a toe in the 5.x water, following your own pace. You surely don’t want to be late here!
So with all this being said, of course you must remain reasonable. If you asked me, “should I migrate my existing project to eZ Publish 5.0?”, the answers are obviously not the same. The three reasons above pushing in favor of a YES are totally valid but you obviously must take into consideration a bunch of other very important operational matters like how to deal with the migration, the change, the impact on the infrastructure, the risk of this in parallel of a running application. Enough fodder to dedicate to a new blog post!
So of course, don’t be blind and plan carefully for any upgrade, even though using the latest stable version is always very good in itself! In any upgrade consideration, we definitely advise you and your team to take the time to learn, experience and understand how 5.x works both with the legacy architecture and the new one. This will help to plan a smooth and progressive upgrade which may mean sticking to the legacy architecture first and then progressively migrating part of your project to the new template engine... More than anything, here we recommend to dedicate some time for your developers to test and learn before working on a project in production. And yes it might be that in some case, the time to do this takes you to 5.1 or further. That is the normal life of a CXM (Customer Experience Management) project, they can’t always upgrade every 6 months or even every year!