9 issues have been successfully integrated with 1 rejected and 15 in the queues (*). That's 90% accuracy!
(*) From now, we'll stop reporting delayed issues, but will report queues status always. Queues include any issue sent to integration (regardless it is in the candidates or the current picker), so it will display a more accurate number of the pending issues to process.
- Moodle 3.10.4, 3.9.7, 3.8.9 and 3.5.18 minors were released last week and Moodle 3.11.0 was released this Monday. Check out the releases page to see the main changes on each version and the new feature page to know the main improvements of Moodle 3.11. 🧐
- Some modifications are coming over the next few days related to the way issues are processed and sent to the current integration picker in order to achieve a, hopefully better, continuous flow of issues. Stay tuned 😉
- There are 57 issues awaiting peer review. Let's keep this number lower... Will we be able to down to 50 before the next post?? 💪
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-6321, had an agreement some weeks ago and now, if a patch introduces a change on the front end, an optional accessibility check can be done during peer reviews. This item was added to the Peer review checklist (thanks for taking care of that, Jun!!). 👏
- MDLSITE-6397 is the next one in the list, to clarify rules on file termination both in coding style and in CI. Time to comment and/or vote! "Do not put off till tomorrow what you can do today. ". Remember cutoff will happen next Friday at 00:00 UTC. 🗃️
- To everybody who has contributed to Moodle 3.11, regardless of their role and task (a lot of grains of sand are required for building a beach!). It's amazing and super exciting to see how Moodle keeps growing thanks to you all! #ProudOfMoodleCommunity 🤩