Ibexa DXP release process and roadmap¶
Ibexa DXP has three distributions:
- Ibexa Content is a multichannel and headless content management system.
- Ibexa Experience is a modern modular Digital Experience Platform to build outstanding customer experiences
- Ibexa Commerce is a commerce-ready B2B DXP designed to digitalize your business from customer awareness to purchase and beyond.
Additionally, Ibexa DXP also has an open-source version called Ibexa OSS. Ibexa OSS is developed by Ibexa together with the open source community. The Ibexa OSS code is available on GitHub under the GPLv2 license. It comes with no commercial support and maintenance services.
We manage the release of Ibexa DXP using an agile iterative process and a continuous software development model, which is why we provide two kinds of Ibexa DXP releases:
- Long Term Support releases (LTS) which are supported by Ibexa for a long period of time (see support lifecycle below).
- Fast Track releases (FT) give access to the latest features and are supported for a short period of time. They are maintained only until the next FT release is introduced.
FT releases are tailored for those who want to stay up-to-date with newest functionalities, while LTS releases are suitable for highly stable enterprise rollouts.
We usually release Ibexa DXP four times a year following the seasons (winter, spring, summer and fall). This usually includes one LTS release and three FT releases.
All Ibexa DXP editions use semantic versioning.
The version number of Ibexa DXP and all its internal components follows the semantic versioning conventions: vX.Y.Z.
- Changes to X indicate breaking changes. They usually concern mostly internal things, but developers should check in our change logs if they need to adjust their code to continue using the API or features. If there are larger breaks, this is announced well in advance of the upcoming release.
- Y represents new features and functionalities.
- Z represents patches, bug fixes, smaller improvements, etc.
Distribution files of our three editions are as follows:
- for Ibexa Content: ibexa-content-vX.Y.Z.tgz
- for Ibexa Experience: ibexa-experience-vX.Y.Z.tgz
- for Ibexa Commerce: ibexa-commerce-vX.Y.Z.tgz
Our software products are continuously evolving. With each release we strive to release stable products with cutting-edge technology. This means there is need for software maintenance services to provide bug fixes and adjustments. As our products constantly 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.
That is why our support and consulting professional services teams are available to assist as part of an Ibexa DXP 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 looking for the latest features. 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.
You can find the specific dates of service life for each release on our support portal service life page.
Our roadmap is updated continuously following our iterative development methodology (our own adaptation and combination of Scrum and Kanban). Our agile boards offer a clear view of the ongoing and upcoming development and are open to the public. 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 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 firstname.lastname@example.org.