Background

Moodle 4.0 was released on the 19th April 2022 and the Moodle community has started to update their plugins for this version.

With our codebase on 3.11 and failing tests reduced significantly through TI2 & TI3 21/22 leveraging our new optimised testing pipeline, and operational issues drawn down in TI4, we now need to ready UCL's Moodle codebase for Moodle 4.0. Moodle 4.1 is expected on the 14th November, in sprint 2, 28th November, in sprint 3, so we should leap ahead towards working against that version as soon as ready. However, the plan remains for the upgrade to Moodle 4.2 to take place in summer 2023.

In Scope:

1) Review progress by upstream maintainers in fixing test failures we reported

Moodle 4.0 upstream logged issues

2) Get Catalyst to finish fixing the code maintenance tickets

https://wrms.catalyst.net.nz/wr.php?request_id=348446

https://wrms.catalyst.net.nz/wr.php?request_id=363070

3) Start manually testing & fixing the UCL developed plugins for 4.1

https://github.com/orgs/ucl-isd/repositories?q=moodle-plugin-ucl&type=all&language=&sort=

https://github.com/uclmoodle

make sure they all have moodle-plugin-ci Github Actions setup & deal with feedback. 

Add appropriate Unit tests - the following manual test scripts are probably a good set to start automating as Behat - Bespoke UCL plugins- testing scripts &  Tests-MyFeedback

4)  Identify "abandoned" plugins we need to take ownership of & start fixing

We need to identify abandoned plugins for which UCL needs to take ownership of plugin maintenance. Start fixing failures on those specifically.

Initial list aware of includes:

• format_flexible
• mod_structlabel
• qtype_algebra
• qtype_jme
• atto_pastespecial
• finish the chemrender updating (Catalyst?)
• any others?

https://github.com/ucl-isd?q=moodle-plugin-adoption

5) Spin up a Moodle 4.1 Preview instance and build branch (rebase changes required from 3.11 prod) . (sprint 2)

And spin up the Major Upgrade Moodle Testing Strategy for it

Start testing with a 4.1 beta build as code freeze has passed but release date pushed back to 28th November.

6) Once all the above is complete, we can start fixing remaining issues in unit tests & community plugins

this part probably more of a TI2 thing

Out of Scope:

Acceptance Criteria to include