Affects Version/s: Future Dev
Fix Version/s: None
We need to decide ASAP about all the PHP/DB/Moodle versions requirements and put all them into the environmental tests (adding them to all supported branches).
All the still open linked issues have been also cloned here from the 4.0 sister issue (
- PHP min. version/supported versions.
- database versions.
- Linked issues.
Feel free to propose areas to be discussed here. A numbered list with all them will be created to vote and decide the final outcomes of this issue.
TODO-1: Once the agreement is settled, if there are raised requirements (PHP/Database/Extensions...) create a MDLSITE issue to ensure that external testers environment is ready for them.
TODO-2: Once the agreement is settled, ensure that the affected php docker images fulfill all the requirements (extensions...). Same for (still) non-dockered stuff, like legacy CI server or performance-comparison jobs.
TODO-3: Raised lower PHP version do imply that both moodlehq/behat-extension and core composer stuff need to be updated and regenerated with it. Followup issue.
TODO-4: Once the patch is ready to peer-review, update all the configuration @ CI infrastructure (nightlyjobs) to ensure that every Moodle branch knows its lowest and highest PHP supported versions.
TODO-5: Once applied upstream, changes are needed @ download.moodle.org to show the new requirements there (serverscripts).
TODO-6: Once applied upstream, ensure that the corresponding release page has the correct agreed requirements updated (ask the Community team if the page is still missing).
TODO-7: Once applied upstream, ensure that both the Mac and Windows packages fulfill the requirements and work ok.
TODO-8: Once applied upstream, review the travis and/or github actions configuration for various repositories. The new core requirements may be hitting them. Also add new branches if missing. Known to need review / fix repos include:
- moodle_docker (both CIs and default php/db versions if raised)
- moodle-ci-runner (both CIs and default php/db versions if raised)
TODO-9: Consider if there is any PHPUnit upgrade to perform whenever there are PHP version changes.
TODO-10: Ensure that the (clone of this) issue for next (to this) requirements issue is created and contains all the information. All the non-resolved details and issues must be dragged to the new issue.
TODO-11: Ensure that there are landing pages @ docs for all the environmental changes performed.
TIA and ciao