Release process

Claroline releases follow the semantic versioning strategy, and they are published through a time-based model:

• A new Claroline patch version (e.g. 13.0.46, 13.1.1) comes out every week (on Wednesday). We may release additional patch versions if we need to fix production blocking bugs. It only contains bug fixes, so you can safely upgrade your applications;
• A new Claroline minor version (e.g. 13.1, 13.2) comes out every month. It contains bug fixes and new features, but it doesn’t include any breaking change, so you can safely upgrade your applications;
• A new Claroline major version (e.g. 13.0, 14.0) comes out roughly every year. It can contain breaking changes, so you may need to do some changes in your applications before upgrading.

Major version release

In each major release :

• We remove all the Updater classes.
• We remove all the Migrations and generate only one per bundle based on the current entities state.
• We empty the claro_version table to only keep the latest installed version.

That’s why it is required to upgrade to the last version before upgrading to the new major version. For example, before upgrading to 14.0.0, you’ll need to update your platform to the last 13.x before jumping on the 14.