Agreed TI2 - 2021/22 - Should do - Moodle 4.0 - Prepare codebase for 4.0 Upgrade

Size

Medium 

Budget Epic Name

Moodle 4

Jira Epic

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Feature LeadEhsan Anwar


Background

With the work done on the Moodle technical Pipelines in TI1 we are now able to re-run our builds with full behat & PHPUnit test suites completed within 3.5h.

Following on from this success we now need to ready UCL's Moodle codebase and pipelines for the summer Moodle 4.0 upgrade.


Focus on the 3.11 - we will aim for 3.11.x upgrade to happen in March release - Moodle 3.11.6 - Annual Upgrade


In Scope:

1) The first step would be to fix all the PHPUnit & Behat errors against Moodle 3.11

Moodle Testing Strategy for 3.11 - this was put in place in case we were going to upgrade to 3.11 last year but it would likely be good to have a clean build before tackling the 4.0 changes.


2) Continuously fix PHPUnit & Behat errors against Moodle 4.0 beta

We know the Moodle 4.0 release has been delayed and is now expected in March 2022 but we can build upon the work in 1) and get our 4.0 build to also pass all of the automated tests


3) Manual Testing of all of the plugins

This is usually a last resort but with the changes in 4.0 navigation being so significant it seems sensible to do this.


4) The last of the major Moodle bug/Issue trackers need to be completed.


5) Will need to fix & adapt UCL developed plugins to work with Moodle 4.0.

  • We may also need to take on the ownership of abandoned plugins to get them ready for 4.0 if we still value them.


Fix issues ourselves

Where feasible we should fix the issues ourselves, however if the particular issue needs an actual developer to be involved, these can be done through our development framework as we will not have any internal capacity for this in TI2.


Out of Scope:


Acceptance Criteria to include