=20
=20
- Release =
Process
=20
- V=
ersioning Conventions
=20
- Support Life Cycle
=20
- Roadmap=20
=20
- How t=
o Read the Board
=20
- Want =
to Contribute?
=20
=20
=20
=20
- =20
- =20
- Release = Process =20
- V= ersioning Conventions =20
- Support Life Cycle =20
- Roadmap=20
- =20
- How t= o Read the Board =20
- Want = to Contribute? =20
=20
Link to this page? Please =
use the permalink http://doc.ez.no/roadmap url.
![](rc=3D"/download/attachments/31426512/space-shuttle.png?version=3D1&modi=)
Release Proces= s
This document explains the release process for eZ Platform and eZ Enterp= rise.
eZ Platform is an open source Content Management S= ystem (CMS) developed by eZ Systems together with the open source community= . eZ Platform's code base is available on GitHub= under the GPLv2 license.
eZ Platform Enterprise Edition (EE) is a commercia= l software available under eZ Business User License, comprised of eZ Platfo= rm Open Source edition and additional features provided as part of the = ;Studio feature set.
The eZ Platform release and support cycle is = described below.
We manage the release of eZ Platform using an agile iterative p= rocess and a continuous software development m= odel.
There are two kinds of eZ Enterprise releases:
- Long Term Support releases (LTS) which are suppor= ted by eZ Systems for a long period of time (see support lifecycle below), = for eZ Enterprise subscribers.
- Fast Track releases (FT) which are supported= for a short period of time, only until the next FT release is introduced. = These are supported for both the open source community and eZ Enterpri= se subscribers.
Version= ing Conventions
eZ Pla= tform Open Source and Enterprise editions use Semantic Versioning.
eZ Pla= tform and all inner components have a version number following the semantic= versioning conventions vX.Y.Z.
- Chang= es to X, the first digit indicate a breaking change to the API, and develop= ers know that they may need to implement a re-write of their code to contin= ue consuming the API moving forward.
- Y, th= e middle digit represents new features and functionality.
- Z, Th= e final digit represents patches, bug fixes and other forms of =E2=80=9Coop= s=E2=80=9D and =E2=80=9Caha!=E2=80=9D.
In add= ition to the version number, we communicate on eZ Platform Enterprise relea= ses using their release name, which provide information on the support and = maintenance service availability. Example: eZ Platform Enterprise 2017<= /em> for the Long Term Supported release that came mid December 2016 o= r eZ Platform Enterprise 2017.04 for the Fast Track release that c= omes in April 2017.
This way, distribution files of our product are as following:
eZ Platform uses its own unique seman= tic version number: ezplatform-vX.Y.Z.tgz
eZ Platform Enterprise uses its= semantic version number: ezplatformenterprise-vX.Y.Z.tgz
Support Life Cycle
Our software products are continuously evolving, and we have released ma= ny versions over the years.
As we strive to release stable products with cutting-edge technology, th= ere is an obvious need for Software Maintenance services to provide bug fix= es as well as adjustments for evolving web technologies. And, as our p= roducts always provide new features and possibilities, our documentation an= d user forums may not always be able to provide an answer to all questions = that may arise. That's why our Professional Services Team<= /a> 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 featur= es and extensibility. We adapt to this continuous evolution by phasing out = services for the old versions while commencing services for the new ones.&n= bsp;This means that our services specific to each release are only availabl= e 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
Product Release |
First Ship Month (FSM) | Last Ship Month (LSM) | End of Service Life (EOSL) |
Service Life Extension (SLE)= |
|---|---|---|---|---|
| eZ Platform April 2017 FT | Planned for end of April 2017 | June 2017 | N/A (Fa= st Track) | N/A (Fa= st Track) |
| eZ Platform February 2017 FT (v1.8) | Planned for end of February 2017 | April 2017 | N/A (Fa= st Track) | N/A (Fa= st Track) |
| eZ Platform 2017 LTS (v1.7) | December 2016 | December 2017 | End of December 2019<= /td> | TBD |
| eZ Enterprise 2016.10 FT (v1.6) | October 2016 | December 2016 | N/A (Fast Track) | N/A (Fast Track) |
| eZ Enterprise 2016.08 FT (v1.5) | August 2016 | October 2016 | N/A (Fast Track) | N/A (Fast Track) |
| eZ Enterprise 2016.06 FT (v1.4) | June 2016 | August 2016 | N/A (Fast Track) | N/A (Fast Track) |
| eZ Enterprise 2016.04 FT (v1.3) | April 2016 | June 2016 | N/A (Fast Track) | N/A (Fast Track) |
| eZ Enterprise 2016.02 FT (v1.2) | February 2016 | April 2016 | N/A (Fast Track) | N/A (Fast Track) |
eZ Enterprise 2015.12 FT (v1.0) |
December 2015 |
February 2016 |
N/A (Fast Track) |
N/A (Fast Track) |
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 2013** |
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 P= ublish Enterprise 4.4 |
Sept= ember 2010 |
Sept= ember 2011 |
End = of September 2014 |
Elig= ible. End of September 2016 |
eZ P= ublish 4.3 |
Marc= h 2010 |
Marc= h 2011 |
End = of March 2014 |
Elig= ible. End of March 2016 |
Releases preceding eZ Publish 4= .3 have all reached their end of Service Life. |
- FSM: The First Ship Month we accept installations to start using this v= ersion.
- LSM: The Last Ship Month we accept installations to start using this ve= rsion.
- EOSL: End Of (normal) Service Life, the last month we provide Product S= upport and Software Maintenance services for a given version.
- SLE: Extended Software Maintenance which includes security updates beyo=
nd EOSL. Contact your sales representative for more details.
- Note: SLE is a "best effort" product with no bug fix guarantee. Hen= ce, under SLE it is not recommended to do new developmen= t like redesign, moving to new servers, new server operating system or simi= lar. For such efforts, please upgrade to a version within normal service li= fe first.
- LTS: Long term supported release
* For individually agreed lengths of Service Life, please consult y=
our 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 f=
or new customers when 5.1 came out, thus old contracts have an EOSL in Nove=
mber 2016 but we highly recommend that all existing 5.0 customers upgrade t=
o an LTS release.
*** 5.4 introduces new features in "6.0/P=
latform 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 P=
ublish release, it will be available for existing eZ Publish customer beyon=
d Last Ship Month (until EOSL), and have an extended service life, making i=
t an ideal release for slow migration to eZ Platform and eZ Studio.
![]()
Roadmap
Our roadmap is updated continuously following our custom ScrumBan iterat= ive development methodology (our own adaptation and combination of= Scrum and Kanban). 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 Assura= nce, which ensures our ability to deliver a stable first version of the pro= fessionally supported software.
If you want to know what are the EPICS (big features) we are working on,= please look at our dedicated produ= ct development board:
How to Read= the Board
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 dev= eloped already in the last release, or will be in the next one, but might s= till be missing some documentation.
- Dev: Features in progress, unless just started, they w= ill 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 i= n the future.
Work = currently in progress
The following list represents the Epics currently in progress and which = might make it in the next release.
| Key | =20Summary | =20Updated | =20Assignee | =20Reporter | =20P | =20
|---|---|---|---|---|---|
| EZS-1252 | = =20Studio Internationalization (l18n)= | =20Jan 11,= 2017 | =20Unassigned | =20Andr=C3=A9 R=C3=B8mcke = | =20 | =20
| EZS-1253 | = =20Form Builder M2 | =20Jan 18,= 2017 | =20Unassigned | =20Roland Benedetti | = =20 | =20
| EZP-25793 =20 | UDW finder | =20Jan 18,= 2017 | =20St=C3=A9phane Diot =20 | Roland Benedetti | = =20 | =20
| EZP-26647 =20 | Content Type View | =20Jan 25,= 2017 | =20Unassigned | =20Roland Benedetti | = =20 | =20
| EZP-26828 =20 | Tools, documentation and processe= s for contributing translations | =20Jan 30,= 2017 | =20Unassigned | =20Bertrand Dunogier | = =20 | =20
| EZP-25541 =20 | Rich Text Editing M3 | = =20Jan 24,= 2017 | =20Damien Pobel | =20Damien Pobel | =20 | =20
| EZP-25696 =20 | HTTP cache multi-tagging =20 | Jan 24,= 2017 | =20Bertrand Dunogier | = =20Bertrand Dunogier | = =20 | =20
| EZS-1265 | = =20Rename Studio > EE | = =20Jan 04,= 2017 | =20Unassigned | =20David Christian Liedle = | =20 | =20
Next up:= Top of the queue
Below is the first 10 epics we have prioritized to work on next.
| Key | =20Summary | =20Updated | =20Assignee | =20Reporter | =20P | =20
|---|---|---|---|---|---|
| EZS-830 | =20Flex Workflow Create without Publis= h rights | =20Jan 30,= 2017 | =20Unassigned | =20Roland Benedetti | = =20 | =20
| EZS-988 | =20eZ Enterprise on Platform.sh <= /td>=20 | Dec 21,= 2016 | =20Gunnstein Lye | =20David Christian Liedle = | =20 | =20
| EZP-26526 =20 | FieldType UI Doc | =20Nov 28,= 2016 | =20Unassigned | =20Andr=C3=A9 R=C3=B8mcke = | =20 | =20
| EZP-25989 =20 | REST Embedding | =20Jan 16,= 2017 | =20Bertrand Dunogier | = =20Andr=C3=A9 R=C3=B8mcke = | =20 | =20
| EZP-25357 =20 | Rich Text Custom Tag M1 =20 | Jan 18,= 2017 | =20Unassigned | =20Roland Benedetti | = =20 | =20
| EZP-23738 =20 | Permissions UI granularity <= /td>=20 | Jan 17,= 2017 | =20Andr=C3=A9 R=C3=B8mcke = | =20Andr=C3=A9 R=C3=B8mcke = | =20 | =20
| EZP-26866 =20 | POC Hybrid SF app loading YUI mod= ules from 1.x | =20Jan 25,= 2017 | =20David Christian Liedle = | =20Roland Benedetti | = =20 | =20
| EZP-26465 =20 | Search Facets | =20Jan 17,= 2017 | =20Unassigned | =20Andr=C3=A9 R=C3=B8mcke = | =20 | =20
| EZP-25939 =20 | Content on the Fly M2 | = =20Dec 13,= 2016 | =20Damien Pobel | =20Roland Benedetti | = =20 | =20
| EZP-25778 =20 | Display Semantic Version Number i= n UI | =20Nov 05,= 2016 | =20Unassigned | =20David Christian Liedle = | =20 | =20
Want to Con= tribute?
Our process being open, please feel free to report bugs or suggest featu= res via our JIRA projects: the EZP Jira project = for all things related to eZ Platform, and the EZS Jira projec= t for all things related to eZ Studio (the enhanced version of Pla= tform available only with eZ Enterprise).
If you'd like to help speed things up because you need a feature on a pr= oject, Epics in the Open state are relatively sa= fe to jump on.
- Simply add a comment on the one you have already worked on or wou= ld like to start on among the epics= on the board, and folks at eZ will try to help on specifying the featu= re.
- For discussions on how to tackle the feature technically,
- When a Pull request has been opened, most of the discussion will = happen in the relevant github repositories.
- When a feature is done, you can help out on documentation by prop= osing documentation using for instanc= e gist.github.com and link to them via comments on the Epi= cs.