It’s that time of the year again. As the final details are finalized for another exciting major Moodle release, 3.5, developers can leap ahead and ensure that when the time to upgrade comes, users and admins find no issue with their plugins on their new Moodle sites. The reception of the “Early Bird” badge has been enormous and growing. The previous version, Moodle 3.4, broke the record of being the version with the highest number of compatible plugins at the time of launch, with 163.
It will be difficult for Moodle 3.5 to set a new record, though, as the “Early Bird” call, made by Moodle HQ’s David Mudrák, on the Moodle Forum, was made less than a week before launch. Besides, the upgrade to the newest version of the Bootstrap framework, 4, means another set of conditions for plugin developers to fulfill, especially theme developers and those that depend on the framework for their interface or behavior.
Another special matter involves GDPR compliance. As has been reported, Moodle 3.5 will provide compliance to Europe’s new data privacy, user requests, and management of policy agreements and user request requirements. But given the complexities involved, including the possible implementation of the new Privacy API to better manage user information, the “Early Bird” badge can be awarded without the need to comply with GDPR. Instead a “GDPR” badge will be issued later on.
Developers who accept the mission must complete the following instructions:
- Test “intensively” in the Moodle 3.5 Beta release. Mudrák recommends using automated testing tools Behat and PHPUnit.
- Fix all errors, warnings, notices, and regressions. Given the kinds of changes coming with Moodle 3.5, regression testing deserves special attention.
- Release the new plugin updating it on the Moodle plugin directory, marking the compatibility up to Moodle 3.5. Since it is difficult to ensure that the same plugin is compatible with versions previous to 3.3, developers can offer several versions of the plugin catering to different versions.
The Moodle HQ team reserves the right to revoke the badge if they detect issues that could have been prevented with testing.