Cold numbers:
10 issues have been successfully integrated with 0 rejected and 9 delayed. That's 100% success! 👏
Notes:
- After 7 intense weeks, with 318 issues successfully integrated and Moodle 3.9 released, we are back to normal. It's time for celebrations, retrospectives and, of course, to continue planning and preparing the next Moodle version. Stay tuned!
- This is a good time to look at your pending dev docs and complete them for helping everybody else.
- Over the next weeks will be working on every 3.9 regression detected, towards Moodle 3.9.1 release in July 2020.
- There are 95 issues awaiting peer review. Please, help us to reduce this number and push all those issues to integration!!
Will we manage to reduce it to 0 someday?
- If you missed last dev meeting this Tuesday 16 June, where Brendan shared his knowledge in caching and performance and Sander explained latest Moodle news, remember you'll find the recording here.
Hot topics:
- MDL-69049: Moodle 3.9 upgrade fails due to missing column in privacy plugins if standalone GDPR plugins were used
- MDL-68971: The error message when a web service can't be found totally unhelpful
- MDL-68436: Atto recordrtc (record audio/video) plugin only works in the first editor on a page
- MDL-66899: Regrading quiz attempts should be logged
One at a time:
This (non-regular) section in the integration posts aims to get various policy issues communicated and, with your collaboration, decided and applied in an organised way.
- MDLSITE-6087, known as "Require formal namespaces for new files", has been agreed and is now in effect. From now, formal namespaces are required for any new classes in Moodle (except when it doesn't support them). The coding style page will be upgraded soon with the newly agreed rules.
- MDLSITE-6130 is the next policy issue proposed, about requiring new JS modules to be written in ES6. Please, vote your preference to decide whether ES6 should be required or not.
Warm thanks:
- All educators around the world!! 😘