Wednesday 16 May 2012 7:07:46 pm
With Etna (4.7) now out the door, eZ Publish's git repository is now re configured for 5.0.0alpha1, signaling that development of 5.0 has started. This has no effect other then signaling ezpublish repository is about to see some larger changes than you would normally see in the next 4+ months.
5.0 will actually consists of two parts:
Those parts will be tightly integrated together and allow you to use either part side by side or in combination.
IMPORTANT NOTE: But before you read on, do know that we intend to allow your existing 4.x site to work as is and that there is no plan for removing the "4.x stack" for several years to come.
5.0 from a high perspective:
Kilimanjaro has been in development for a bit over a year now, it's been available on github.com/ezsystems/ezp-next for almost just as long. It is intended to become a fully modern HMVC architecture, but so far our main focus has been on the M, the Model, with all APIs and layering (adhering to Separation Of Concern & Domain Driven Development) to allow us to transparently switch to NoSQL in the future, this is thus seen as the largest and most important part of eZ Publish 5. It is a big step up from what you might call APIs in current eZ Publish, and will help you accelerate development and time to market considerably.
The architecture you can find already in ezp-next is:
Not a complete list, but some improvements native to the new Public API:
We have also been working hard on preview of Editorial interface and REST API v2, and as hinted in overview above these parts should be available within the next month.
What you can expect to see:
In addition to REST and Editorial interface we are also working on prototyping the rest of the architecture (the Hierarchical, View and Controller parts of HMVC).
The requirements are:
* We do intend to remove most deprecated features, we are also considering adjusting certain features that should be shared between 4.x and 5.x (Session, SiteAccess, ..) and discussing removing features that do not fully make sense in the 5.x architecture ( first and foremost: a 4.x stack only static cache ).
** We intend to add support for more migration scenarios in "Stetind", the eZ Publish release in May 2013.
More information about this prototype will be available in the beginning of June, stay tuned! :)
Until we start to merge in code to eZ Publish repository and the features described in this blog post start to appear in community builds (eta: mid/end of June), here is currently how you can test out Public API using an existing eZ Publish installation, discuss it in our API forum section and create pull requests:
eZ Publish 5 : Be prepared for the future + with additional information in comments