Chamilo 2.0 alpha 1 - Babaorum, 2024-07-20

Release notes - summary

Chamilo 2.0 will be a major release, a new branch for the Chamilo software. It is based on Chamilo 1.11.10 and includes tons of backend changes that will make developing Chamilo more "mainstream" and (hopefully) faster in the future, by adopting more widely-known libraries, with the notable inclusions of Symfony as a main controller and framework (except for some legacy tools not yet converted), VueJS as our main frontend framework and TailwindCSS as our CSS framework.

For the first time in almost 15 years (since its launch in 2010), Chamilo considerably changes appearance, with a new, foldable, left menu (meant to improve space usage on mobile devices) and a streamlined (and open source) set of icons, and a design that will allow more flexibility and speed across devices.

This is an ALPHA release, meaning it is not finished and is meant for testing and development only. It should *NOT* be used in production unless you have a full-time dedicated IT team behind it.

An alpha version, to us, means that (except for unforeseen issues) the database structure is fixed and the files structure is fixed (although some files could still be added/removed before the beta release).

Release name

Babaorum (ficticious village name, see French art)

Security fixes

Added

.

Changed

Fixed

Known issues

Syntax and terminology

To ensure this changelog is the most useful, we are using a specific syntax and terms for this changelog, provided below.
> Also, this changelog, to the exception of security fixes, only contains elements that have an impact on users. Sysadmins and developers are invited to use git log to find any specific change.

Versions

Each version is shortly described, with:

Sections

Inside each version block, different sections are laid out to ease the reading of the changelog: Within those sections, you will find different markers helping you filtering out specific topics like theming, web services, database, etc.

Syntax

Every change comes with a link to the change in our versions tracking system, a link to the reported issue or task (if any) and a short description of the change's purpose or effect.
A commit message will typically show as follows:
    [Minor: ][Tool: ][Subtool: ][Description][ - refs #1234]
        
where:

Tools/features terminology

We use a short terminology to group all changes applying to the same tool. We use a term in singular even when talking about multiples. The names we use for these tools/features are:

Hashtags

Commit messages must include (at the end) an indication of the *type* of change: Other tags might include:
=