General

  eZ Systems Website


  Developer documentation


  Editor documentation


Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Link to this page? Please use the canonical http://doc.ez.no/roadmap url.

Release process

This document explains the release process of eZ Platform and eZ Studio projects.

eZ Platform is an open-source software developed by eZ together with the eZ community whose code base is available on GitHubeZ Studio is proprietary (commercial) software. Both projects are following the eZ Enterprise release process described below.

eZ manages its release using an agile iterative process and a continuous software development model.

eZ releases are of two kinds:

  • eZ Long Term Supported releases (LT) which are supported by eZ for a long period of time (see below support lifecycle), for eZ Enterprise subscribers.
  • eZ Fast Track releases (FT) which are supported for a short period of time, until a new FT release is introduced. These are supported for both Community and eZ Enterprise subscribers.

 

Support life cycle

Our software products are continuously evolving, and we have released many versions over the years.

We strive to release stable products with cutting-edge technology. However, with new software, there is the inevitable need for Software Maintenance services to provide bug fixes and 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, in which case our Product Support service team stands ready to assist.

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 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.

This table provides an overview of the beginning and end of the Service Life of our products*.

 

Product

First ship month (FSM)

Last ship month (LSM)

End of Service Life (EOSL)

Service Life Extension (SLE)

eZ Enterprise 2016 (15.12)

December 2015

Q4 2016

End of December 2018

Not Eligible

eZ Publish Platform 5.4 LTS***

November 2014

November 2015****

End of November 2017

Eligible. End of November 2021****

eZ Publish Platform 5.3 LTS

May 2014

May 2015

End of May 2017

Eligible. End of May 2019

eZ Publish Platform 5.2

November 2013

May 2014

End of November 2014

Not Eligible

eZ Publish Platform 5.1 LTS

May 2013

May 2014

End of May 2016

Eligible. End of May 2018

eZ Publish Platform 5.0

November 2012

May 2013**

End of November 2016**

Not Eligible

eZ Publish Enterprise 4.7

May 2012

May 2013

End of May 2015*

Eligible. End of November 2017

eZ Publish Enterprise 4.6

November 2011

November 2012

End of November 2015

Eligible. End of November 2017

eZ Publish Enterprise 4.5

March 2011

March 2012

End of March 2015

Eligible. End of March 2017

eZ Publish Enterprise 4.4

September 2010

September 2011

End of September 2014

Eligible. End of September 2016

Releases preceding eZ Publish 4.4 have all reached their EOSL and their SLE.

  • FSM: The First Ship Month we accept installations to start using this version.
  • LSM: The Last Ship Month we accept installations to start using this version.
  • EOSL: End Of (normal) Service Life, the last month we provide Product Support and Software Maintenance services for a given version.
  • SLE: Extended Software Maintenance which includes security updates beyond EOSL. Contact your sales representative for more details.
    • Note: SLE is a "best effort" product with no bug fix guarantee. Hence, under SLE it is not recommended to do new development like redesign, moving to new servers, new server operating system or similar. For such efforts, please upgrade to a version within normal service life first.
  • LTS: Long term supported release

* For individually agreed lengths of Service Life, please consult your contract. If it goes beyond EOSL it will effectively be valid under the terms of SLE.
** 5.0 was changed to a short term release for new customers when 5.1 came out, thus new contracts have an EOSL in November 2013. We recommend that all existing 5.0 customers upgrade to an LTS release.
*** 5.4 introduces new features in "6.0/Platform stack" and will continue to get certain new features during 2015 to ease forward compatibility with eZ Platform and eZ Studio. For further information see 5.4 release notes.
**** 5.4 being the last eZ Publish release, it will be available for existing eZ Publish customer beyond Last Ship Month (until EOSL), and have an extended service life, making it an ideal release for slow migration to eZ Platform and eZ Studio.

Roadmap

eZ roadmap is updated continuously following our iterative development methodology (an adaptation and combination of Scrum and Kanban that we continuously adapt). Our agile board is open so that anyone can have a clear view of the ongoing and upcoming development. Progress is based on the prioritized Epics 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 what are the EPICS (big features) we are working on, please look at our dedicated product development board:

How to read?

The Epic board can at first be daunting to understand, so here are some things to be aware of:

  • Doc: Means the feature has most likely either been developed already in the last release, or will be in the next one, but might still be missing some documentation.
  • Dev: Features in progress, unless just started, they will be part of the next upcoming release (barring some roadblocks).
  • Prioritized/Spec: These are the next features we will start working on, prioritization and main responsibility to specify is done by eZ Product Management team.
  • Open: A backlog of features we want to have in place in the future.

Work currently in progress

The following list represents the Epics currently in progress and which might make it in the next release.

Loading
Key Summary Updated Assignee Reporter P
EZEE-1728 eZ Platform 2 Architecture Simplification Sep 21, 2017 Unassigned Roland Benedetti High
EZP-27807 URL alias Management V2 Mar 27, 2018 Unassigned Supriya Bhargava High
EZP-27487 Content editing in hybrid UI Jul 26, 2017 Gunnstein Lye Bertrand Dunogier High
EZP-22948 Site Design/Theme system Sep 29, 2017 Unassigned Jérôme Vieilledent High
EZP-26310 Docker-Tools / deployment M2 Sep 20, 2017 Unassigned André Rømcke High
EZEE-1602 Provide eZ Personalization as a Service in eZ Platform (open source and enterprise editions) Aug 07, 2017 Unassigned Michael Friedmann High
EZP-27799 Section Management Sep 27, 2017 Unassigned Supriya Bhargava High
EZP-28211 Use user-defined timezone to display dates in Admin U.I. Aug 22, 2018 Unassigned Sylvain Guittard High
EZP-30392 Drop deprecated code from ezpublish-kernel Jun 19, 2019 Andrzej Longosz Sylvain Guittard High
EZP-30690 ConfigResolver is being used too early Jun 26, 2019 Andrzej Longosz Andrzej Longosz High

Next up: Top of the que 

Below is the first 10 epics we have prioritized to work on next.

Loading
Key Summary Updated Assignee Reporter P
EZEE-1505 Cluster support for Platform.sh Cloud System Feb 06, 2018 Unassigned David Christian Liedle High
EZP-27688 Design Improvements Dec 01, 2017 Unassigned Sylvain Guittard High
EZEE-1684 Flexible Landing Page Content Type Feb 16, 2018 Unassigned Roland Benedetti High
EZP-27808 Managing translations and versions Aug 31, 2017 Unassigned Supriya Bhargava High
EZEE-1479 Studio Block Management Jun 02, 2017 Unassigned Supriya Bhargava High
EZP-25388 Symfony 3.x compatibility Aug 21, 2017 Unassigned André Rømcke High
EZEE-1443 File Import M2 Jun 12, 2017 Unassigned Supriya Bhargava High
EZP-26526 FieldType UI Doc Mar 30, 2017 Unassigned André Rømcke High
EZP-26993 Rich Text Editor M4 Apr 18, 2017 Unassigned Roland Benedetti High
EZP-26035 Content Tagging M1 Apr 18, 2017 Unassigned Roland Benedetti High
Showing 10 out of 31 issues Refresh

Contribute?

Our process being open, please feel free to report bugs or suggest features via our JIRA projects: the EZP Jira project for all things related to eZ Platform, and the EZS Jira project for all things related to eZ Studio.

If you'd like to help speed things up because you need a feature on a project, Epics in Open state is relatively safe to jump on. 

  1. Simply add a comment on the one you have already worked on or would like to start on among the epics on the board, and folks at eZ will try to help on specifying the feature.
  2. For discussions on how to tackle the feature technically, or anything else, reach out on Slack using the self service sign on page.
  3. When a Pull request has been opened, most of the discussion will happen in the relevant github repositories.
  4. When a feature is done, you can help out on documentation by proposing documentation using for instance gist.github.com and link to them via comments on the Epics.

 

  • No labels