Whilst we'd all like all Moodle users to be using our latest and greatest code, there is a balance to strike between improving our software and maintaining stability (both in terms of regressions, but also training and documentation materials). Large amounts of change on the stable branches make the lives difficult for institutions to manage upgrades between point releases.
The Component Library is a developer tool provided to help identify frequently-used user interface components, and encourage their re-use.
If you want to contribute to Moodle, you can start looking at the following:
Deprecation, in its programming sense, is the process of taking older code and marking it as no longer being useful within the codebase, usually because it has been superseded by newer code. The deprecated code is not immediately removed from the codebase because doing so may cause regression errors.
Information about past and upcoming developer meetings
A summary of the various development processes used in Moodle development.
- Set up your development environment
All the information related to the integration review process during the Moodle development.
All the information related to the peer-reviewing process during the Moodle development.
All the information related to the Qualify Assurance tests during the Moodle development.
This page lists all official releases of Moodle, grouped by branch in reverse chronological order.
Our Moodle Products roadmap is designed to provide visibility on the development priorities of the Moodle HQ Product teams and covers all the products in our open source learning platform portfolio, consisting of Moodle LMS, Moodle Workplace, MoodleCloud, MoodleNet, Moodle Apps, Moodle Community Sites, and Moodle Academy.
All the information related to testing during the Moodle development.
All the information related to the integration review process during the Moodle development.
A summary of the most common actions in Moodle tracker.