Link to this page? Please use the permalink
This document explains the release process for eZ Platform in it's two flavors:
We manage the release of eZ Platform using an agile iterative process and a continuous software development model, which is why we provide two kinds of eZ Platform releases:
FT releases are tailored for those that want to stay more on the bleeding edge, while LTS releases are suitable for highly stable enterprise rollouts.
We usually releases eZ Platform four times a year following the seasons (Winter, Spring, Summer and Fall). This usually includes one LTS release and three FT releases.
eZ Platform Open Source and Enterprise editions use Semantic Versioning.
eZ Platform and all inner components have a version number following the semantic versioning conventions vX.Y.Z.
This way, distribution files of our product are as following:
eZ Platform uses its own unique semantic version number: ezplatform-vX.Y.Z.tgz
eZ Platform Enterprise uses its semantic version number: ezplatformenterprise-vX.Y.Z.tgz
Our software products are continuously evolving, and we have released many versions over the years.
As we strive to release stable products with cutting-edge technology, there is an obvious need for Software Maintenance services to provide bug fixes as well as adjustments for evolving web technologies. And, as our products always provide new features and possibilities, our documentation and user forums may not always be able to provide an answer to all questions that may arise. For that, our support and consulting professional services teams are available to assist as part of an eZ Enterprise subscription or as part of a specific statement of work. Contact our Sales team for more information.
Over time, existing product versions mature and new versions become the center of attention for customers wanting the latest and greatest in features and extensibility. We adapt to this continuous evolution by phasing out services for the old versions while commencing services for the new ones. This means that our support and maintenance services specific to each release are only available from a given start date until an end date. The time in between the start and end dates is what we call the product's Service Life.
To know the specific dates of service life for each release, please visit our support portal service life page.
Our roadmap is updated continuously following ourd iterative development methodology (our own adaptation and combination of Scrum and Kanban). Our agile boards are open so that anyone can have a clear view of the ongoing and upcoming development. Progress is based on the prioritized stories from a living backlog into phases of specification and design, development and documentation, and QA. The final phase of our development includes a dedicated period of Certification and Quality Assurance, which ensures our ability to deliver a stable first version of the professionally supported software.
If you want to know more, please contact email@example.com
Our process being open, please feel free to report bugs via our JIRA projects: the EZP Jira project for all things related to eZ Platform, and the EZEE Jira project for all things related to eZ Platform Enterprise Edition. If you want to suggest a specific feature for a future release, please suggest the feature on https://ezplatform.com/Product-Feedback clicking on the "submit idea" link.
If you'd like to help speed things up by suggesting code because you need a feature on a project, you are more than welcome to submit your contribution. Some good practice to follow for a smooth contribution