• En
  • Fr
  • Es

Methodology : the development of the Claroline kernel

Needs analysis

According to the needs and feedbacks coming from the users, administrators and developers, the Steering Committee, currently composed of the CERDECAM (ECAM – HELDV) and the IPM (UCL), defines the developments and refactoring that will be realized in the next version of Claroline. 

Structural conception 

The development teams realize a conceptual analysis and makes structural and usability choices. A technical meeting between the different partners validates the choices. 

Development and tests 

The development and the tests are carried out in several phases: 

1. Development version : as soon as a development is realized, it is published on the CVS (Control Version System).

2. Alpha version : this first version aims at validating the different choices. A phase of intensive tests enables to stabilize the development. No functionality is added after that.

3. Beta version : the upgrade tool is built to pass from a version to another. The community feedbacks help to correct the bugs. This version also enables to test the integration of the different developments in the platform.

4. Release candidate version : the new version is installed on two campuses in production whose configurations are totally different:

    • Linux server and http Apache server
    • Windows server and IIS server

5. Stable version : when the stable version 1.x.0 is viewed as stable, it is announced and published on the Claroline website.  

Other stable versions (1.x.1, 1.x.2…) are published according to the problems encountered by the community. Generally, there is no functionality added to these stable versions.

Image