1. 07 Oct, 2021 1 commit
  2. 06 Oct, 2021 1 commit
  3. 01 Oct, 2021 2 commits
  4. 29 Sep, 2021 3 commits
  5. 23 Sep, 2021 1 commit
  6. 22 Sep, 2021 2 commits
  7. 21 Sep, 2021 1 commit
  8. 14 Sep, 2021 1 commit
  9. 09 Sep, 2021 2 commits
  10. 03 Sep, 2021 1 commit
  11. 24 Aug, 2021 1 commit
    • Eloy Lafuente's avatar
      MDL-71847 course: small tests fixes. · a65c0bbc
      Eloy Lafuente authored
      1) Namespace must match the one being covered.
      2) the @covers annotation was wrong, missing class name(s). At the
         end I've used the coversDefaultClass annotation that allows to
         specify a whole namespace, useful in this case to get the 3
         existing (course, section, cm) classes covered.
      a65c0bbc
  12. 23 Aug, 2021 1 commit
  13. 20 Aug, 2021 2 commits
  14. 09 Jul, 2021 1 commit
  15. 29 Jun, 2021 1 commit
  16. 28 Jun, 2021 2 commits
  17. 18 Jun, 2021 1 commit
  18. 12 May, 2021 1 commit
    • Eloy Lafuente's avatar
      MDL-71583 versions: Add all the missing full-stops to version/requires · 9d6aa399
      Eloy Lafuente authored
      It seems that the new phpcs3 checker is now controlling those
      line comments that previously were ignored.
      
      This commit just looks for all the cases and bulk-add
      them when needed. The bash script (mac) used to add all them is:
      
      while read -r line; do
          arr=(${line//:/ })
          if [[ -n ${arr[0]} ]] && [[ -n ${arr[1]} ]]; then
              echo "  file ${arr[0]}, line ${arr[1]}"
              sed -i "${arr[1]}s/\$/\./" ${arr[0]}
          fi
      done < <(find . -name version.php | xargs ag --nomultiline '>(version|requires) *=.*//.*[^;\.]$')
      9d6aa399
  19. 12 Apr, 2021 1 commit
  20. 12 Mar, 2021 2 commits
  21. 14 Jan, 2021 1 commit
    • Eloy Lafuente's avatar
      MDL-69308 upgrade: remove all the < 3.6.0 upgrade steps · 77342b96
      Eloy Lafuente authored
      This just deletes all the upgrade steps previous to 3.6.0. Some
      small adjustments, like tweaking globals can also be applied
      when needed.
      
      Also includes an upgrade step to prevent upgrading from any
      version < 2018120300 (v3.6.0) as anti-cheating measure.
      
      Note that in this case, there wasn't any case of upgradelib
      functions being used, hence we haven't to deprecate/remove
      anything in codebase. When there is such a need, that is done
      in separate commits (one for each function) and documented here.
      
      See MDL-65809 commits for an example removing/deprecating a
      good number of functions.
      77342b96
  22. 23 Nov, 2020 1 commit
  23. 17 Nov, 2020 1 commit
  24. 21 Oct, 2020 1 commit
    • Eloy Lafuente's avatar
      MDL-67673 phpunit: Fix the return type of template methods · f6711bb3
      Eloy Lafuente authored
      All the setup/teardown/pre/post/conditions template methods
      now are required to return void. This was warned with phpunit 7
      and now is enforced.
      
      At the same time, fix a few wrong function names,
      provider data and param types, return statements...
      f6711bb3
  25. 11 Sep, 2020 1 commit
  26. 18 Aug, 2020 2 commits
    • Eloy Lafuente's avatar
      MDL-69475 backup: Proper handling of backup::RELEASE versions · b7100ae5
      Eloy Lafuente authored
      1) Remove any floatval() casting. They are breaking / killing
         .10 versions (converting them to .1). Since Moodle 2.0 all the
         backup::RELEASE have been 100% numerical values.
      2) Use version_compare() always to compare backup::RELEASE values.
         They are always versions and the function is aware of versions
         > .9, able to clean/ignore alpha chars... and everything else.
      
      Note that I've also changed a couple of cases in formats (topics and
      weeks) that were correct, but just added the same comment and used
      the same version_compare() comparison parameters style, so all uses
      in core are consistent (and safe to be copied out there).
      b7100ae5
    • Eloy Lafuente's avatar
      MDL-69475 versions: bump all versions and requires in master · fbb07675
      Eloy Lafuente authored
      version = 2021052500 release version
      requires= 2021052500 same than version
      
      Why 20210525? (25th May 2021) ?
      
      Because master is going to be Moodle 4.0, to be released
      on November 2021. And, until then, we are going to have
      a couple of "intermediate" releases:
      
      - Moodle 3.10 to be released 9th November 2020. (2020110900)
      
        This version will be using versions from today to 2020110900
        (once it's released the YYYYMMDD part stops advancing).
      
      - Moodle 3.11 to be released 10th May 2021. (2021051000)
      
        This version will be using versions from 3.10 release to 2021051000
        (once it's released the YYYYMMDD part stops advancing).
      
      That means that all versions from today to 2021051000 are going
      to be used by those 2 "intermediate" releases (3.10 and 3.11).
      
      And we cannot use them in master, because it's forbidden to have
      any overlapping of versions between branches (or different upgrade
      paths will fail).
      
      So, get that 2021051000, let's add it a couple of weeks to cover
      the on-sync period (or a 2 weeks delay max!) and, the first version
      that master can "own" in exclusive (without any overlap) is, exactly,
      25th May 2021, hence our 20210525.
      fbb07675
  27. 17 Aug, 2020 1 commit
    • Eloy Lafuente's avatar
      MDL-69475 versions: bump all versions and requires in master · 45ce46f2
      Eloy Lafuente authored
      version = 2021052500 release version
      requires= 2021052500 same than version
      
      Why 20210525? (25th May 2021) ?
      
      Because master is going to be Moodle 4.0, to be released
      on November 2021. And, until then, we are going to have
      a couple of "intermediate" releases:
      
      - Moodle 3.10 to be released 9th November 2020. (2020110900)
      
        This version will be using versions from today to 2020110900
        (once it's released the YYYYMMDD part stops advancing).
      
      - Moodle 3.11 to be released 10th May 2021. (2021051000)
      
        This version will be using versions from 3.10 release to 2021051000
        (once it's released the YYYYMMDD part stops advancing).
      
      That means that all versions from today to 2021051000 are going
      to be used by those 2 "intermediate" releases (3.10 and 3.11).
      
      And we cannot use them in mater, because it's forbidden to have
      any overlapping of versions between branches (or different upgrade
      paths will fail).
      
      So, get that 2021051000, let's add it a couple of weeks to cover
      the on-sync period (or a 2 weeks delay max!) and, the first version
      that master can "own" in exclusive (without any overlap) is, exactly,
      25th May 2021, hence our 20210525.
      45ce46f2
  28. 06 Jul, 2020 1 commit
  29. 23 Jun, 2020 1 commit
  30. 14 Jun, 2020 1 commit
  31. 09 Jun, 2020 1 commit