Cold numbers:
54 issues have been successfully integrated with 5 rejected and 3 delayed. That's 92% success, again!
Notes:
- Today, October 24th, @ 14:00 AU/Perth time, code freeze will happen. That makes the start of the the continuous integration period, 5 weeks countdown, towards Moodle 3.2 release (November 28th).
- In general, new features and improvements won't be allowed after freeze, with everybody working on fixing and testing issues, aiming to bring the max stability and polishing to the new version.
- Next week, the 3.2 quality assurance cycle will start, with every problem detected getting fix priority. Aiming to 100% pass rate!
- Don't forget to be proactive labeling the issues while reporting, triaging, fixing, integrating and testing them. There are a number of processes depending of those labels (user and dev documentation, release notes...) and it's always better to label in excess than missing them.
- Right now there are 19 issues awaiting peer review, let's try to process all those that can be suitable for 3.2.
- No matter the 3.2 major release, we'll be also releasing minor Moodle 2.7.17, 2.9.9, 3.0.7 and 3.1.3 updates in 3 weeks (November 14th).
- OS/Browser/Selenium versions for testing have been fixed for Moodle 3.2 and they will be used for its life cycle.
Hot topics:
- MDL-54945 : Workshop portfolio API integration.
- MDL-45639 : SSO from mobile to web site.
- MDL-45639 : Allow to inject pre-scss to the new Boost theme.
- MDL-53832 : LTI v2.0 support added to enrol_lti.
- MDL-56022 : Assignment offline grading in plain, 1 level, folder.
- MDL-43230 : Manually revoke badges.
- And lots more in areas like themes, messaging, book, unit and acceptance tests, book...
Warm thanks:
- To Ruslan Kabalin, for his continuous help in different areas of Moodle along the years in a supportive and sweet way. And because Open Source matters, you true lovers!
For me, open source is a moral thing.
--- Matt Mullenweg