Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-70594

Decide Moodle 4.0 requirements and push them to environment.xml (due date: 2021-06-09)

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 3.9.8, 3.10.5, 3.11.1
    • Component/s: Installation
    • Labels:
    • Affected Branches:
      MOODLE_400_STABLE
    • Fixed Branches:
      MOODLE_310_STABLE, MOODLE_311_STABLE, MOODLE_39_STABLE
    • Pull 3.9 Branch:
    • Pull 3.10 Branch:
      MDL-70594_310
    • Pull 3.11 Branch:
      MDL-70594_311
    • Pull Master Branch:
    • Testing Instructions:
      Hide

      0 - Prerequisites

      1. Ensure that there is NOT any $CFG->moodledata/environment directory in your installation. If it exists... it contains old environment info. Remove the directory completely before continue with the tests below.
      2. Need to test this on all the databases that are affected by the changes (see next section (differences) to check which databases have changed.

      A - On Master, 311, 310 and 39 (all supported and security supported branches):

      1. Go to admin -> server -> environment
      2. One "4.0 upwards" Moodle version should be available.
      3. VERIFY that It shows the same requirements than a 3.11 version but with these differences:
        1. PostgreSQL 10 is required (instead of 9.6).
        2. The exif php extension is recommended.

      B - Verify, for all the numeric (XYZ) branches above, that the environment.xml file is 100% the same (requires git or diff use). All the commands should return NO differences (nothing should be output):

      1. git diff MOODLE_XYZ_STABLE master admin/environment.xml

      C - Upgrade tests (easier with MDK):

      C-1 Using minimum supported version

      1. Install Moodle 3.6.0
        1. Uninstall your current instance

          mdk uninstall -y
          

        2. Checkout the 3.6.0 tag

          git checkout v3.6.0
          

        3. Install

          mdk install
          

      2. Add some courses and one activity or two

        mdk run makecourse
        

      3. Attempt upgrade to master
        1. Checkout the master branch.

          git checkout master
          

        2. Upgrade either via the browser or via CLI (mdk upgrade)
      4. VERIFY: that upgrade works

      C-2 Using older, non-supported version

      1. Install Moodle 3.5.x
        1. Uninstall your current instance

          mdk uninstall -y
          

        2. Checkout the 3.5.0 tag

          git checkout v3.5.0
          

        3. Install

          mdk install
          

      2. Add some courses and one activity or two

        mdk run makecourse
        

      3. Attempt upgrade to master
        1. Checkout the master branch.

          git checkout master
          

        2. Open the moodle instance on your browser
      4. VERIFY: that upgrade is blocked
      Show
      0 - Prerequisites Ensure that there is NOT any $CFG->moodledata/environment directory in your installation. If it exists... it contains old environment info. Remove the directory completely before continue with the tests below. Need to test this on all the databases that are affected by the changes (see next section (differences) to check which databases have changed. A - On Master, 311, 310 and 39 (all supported and security supported branches): Go to admin -> server -> environment One "4.0 upwards" Moodle version should be available. VERIFY that It shows the same requirements than a 3.11 version but with these differences: PostgreSQL 10 is required (instead of 9.6). The exif php extension is recommended. B - Verify, for all the numeric (XYZ) branches above, that the environment.xml file is 100% the same (requires git or diff use). All the commands should return NO differences (nothing should be output): git diff MOODLE_XYZ_STABLE master admin/environment.xml C - Upgrade tests (easier with MDK): C-1 Using minimum supported version Install Moodle 3.6.0 Uninstall your current instance mdk uninstall -y Checkout the 3.6.0 tag git checkout v3.6.0 Install mdk install Add some courses and one activity or two mdk run makecourse Attempt upgrade to master Checkout the master branch. git checkout master Upgrade either via the browser or via CLI ( mdk upgrade ) VERIFY : that upgrade works C-2 Using older, non-supported version Install Moodle 3.5.x Uninstall your current instance mdk uninstall -y Checkout the 3.5.0 tag git checkout v3.5.0 Install mdk install Add some courses and one activity or two mdk run makecourse Attempt upgrade to master Checkout the master branch. git checkout master Open the moodle instance on your browser VERIFY : that upgrade is blocked

      Description

      Policy: PHP & Moodle supported versions

      Since Moodle 3.5 (MDL-59159), these rules apply to decide Minimum PHP and Moodle versions supported:

      1. A LTS will always require the previous LTS (or later) for upgrading.
      2. The maximum PHP version supported for a branch will be the max one achieved along the life of the branch. Usually with .0 releases but may happen later (we added support for php70 with 3.0.1, or support for php73 with 3.6.4, for example).
      3. The minimum PHP version supported for a branch will be the lower of:
        • The minimum version supported in any way by php the day of the Moodle release (so we provide slow, progressive increments).
        • The maximum PHP version supported by the previous LTS branch (so we guarantee jumping between LTS is possible without upgrading PHP at the same time).

      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 3.11 sister issue (MDL-69308).

      Usual discussions:

      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.

       Related Tasks (create issues/PRs whenever they apply):

      TODO-1: MDLSITE-6531 - 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:

      TODO-9: Not needed - Consider if there is any PHPUnit upgrade to perform whenever there are PHP version changes.

      TODO-10: MDL-71747 : 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
       

        Attachments

        1. MDL-70594-A.jpg
          MDL-70594-A.jpg
          411 kB
        2. MDL-70594-B.jpg
          MDL-70594-B.jpg
          27 kB
        3. MDL-70594-C.jpg
          MDL-70594-C.jpg
          137 kB

          Issue Links

            Activity

              People

              Assignee:
              stronk7 Eloy Lafuente (stronk7)
              Reporter:
              sarjona Sara Arjona (@sarjona)
              Peer reviewer:
              Sara Arjona (@sarjona) Sara Arjona (@sarjona)
              Integrator:
              Jun Pataleta Jun Pataleta
              Tester:
              Ferran Recio Ferran Recio
              Participants:
              Component watchers:
              Matteo Scaramuccia, Andrew Lyons, Dongsheng Cai, Huong Nguyen, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                12/Jul/21

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 7 hours, 15 minutes
                  7h 15m