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

Decide Moodle 2.7 requirements and push them to environment.xml

    Details

    • Testing Instructions:
      Hide

      0) To test exclusively in all supported stable branches.
      1) Go to admin -> server -> environment
      2) One "2.7 upwards" Moodle version should be available.
      3) It shows the same requirements than a 2.6 version but with these differences:

      a) verify that zlib is required
      b) verify higher versions of database are required
      c) verify PHP 5.4.x is required

      Show
      0) To test exclusively in all supported stable branches. 1) Go to admin -> server -> environment 2) One "2.7 upwards" Moodle version should be available. 3) It shows the same requirements than a 2.6 version but with these differences: a) verify that zlib is required b) verify higher versions of database are required c) verify PHP 5.4.x is required
    • Difficulty:
      Moderate
    • Affected Branches:
      MOODLE_27_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE, MOODLE_26_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      w51_MDL-42931_m27_env27
    • Story Points (Obsolete):
      13
    • Sprint:
      BACKEND Sprint 8

      Description

      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).

      At the same time, if there is any change in the PHP version... some changes have to be populated to various installers and replace them by the new one when corresponding. To get a list of candidates:

      grep -r '5\.3\.3' * | grep '\.php'

      (and look for MDL-39007 status, about to unify all those duplicated checks)

      Ciao

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  0 Vote for this issue
                  Watchers:
                  19 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    13/Jan/14