Skip to content

Latest commit

 

History

History
63 lines (42 loc) · 3.67 KB

release_process_and_roadmap.md

File metadata and controls

63 lines (42 loc) · 3.67 KB
description
Ibexa DXP releases new versions periodically in different flavors: Ibexa Headless, Ibexa Experience and Ibexa Commerce, plus open-source Ibexa OSS.

Ibexa DXP release process and roadmap

Release process

Distributions

[[= product_name =]] has three distributions:

  • [[= product_name_headless =]] is a multichannel and headless content management system.
  • [[= product_name_exp =]] is a modern modular Digital Experience Platform to build outstanding customer experiences
  • [[= product_name_com =]] is a commerce-ready B2B DXP designed to digitalize your business from customer awareness to purchase and beyond.

Additionally, [[= product_name =]] also has an open-source version called [[= product_name_oss =]]. [[= product_name_oss =]] is developed by [[= product_name_base =]] together with the open source community. The [[= product_name_oss =]] code is available on GitHub under the GPLv2 license. It comes with no commercial support and maintenance services.

Long Term Support releases

[[= product_name_base =]] manages the release of [[= product_name =]] by using an agile iterative process and a continuous software development model, which is why we provide Long Term Support releases (LTS) of [[= product_name =]] releases.

Long Term Support releases (LTS) are supported by [[= product_name_base =]] for a long period of time. They're suitable for highly stable enterprise rollouts.

LTS releases provide you with:

  • Reliability and stability, as they go through extensive testing to ensure they are free from major bugs and issues.
  • Long-term security, as a result of updates and security patches.
  • Predictability that comes from following an established release plan.
  • Reduced maintenance, because you avoid the frequent upgrade cycles.

LTS Updates

With LTS Updates customers can maintain their competitiveness by incorporating cutting-edge technologies into their LTS releases without losing stability. LTS Updates are intended to improve the current platform by providing new features. What's important, you are not required to switch to a newer version of [[= product_name =]] to use LTS Updates. You can install them whenever you choose, and you can be sure that the next LTS release will include them by default. You won't have to manually install or configure them after upgrading, so you can make the switch smoothly when the time comes.

Versioning conventions

All [[= product_name =]] editions use semantic versioning.

The version number of [[= product_name =]] 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, or smaller improvements.

Distribution files of [[= product_name_base =]] three editions are as follows:

  • for [[= product_name_headless =]]: ibexa-headless-vX.Y.Z.tgz
  • for [[= product_name_exp =]]: ibexa-experience-vX.Y.Z.tgz
  • for [[= product_name_com =]]: ibexa-commerce-vX.Y.Z.tgz

[[= product_name_base =]]'s 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 [[= product_name_base =]] calls the product's Service Life.

You can find the specific dates of service life for each release on [[= product_name_base =]] service life page.