1. 28 Sep, 2020 1 commit
  2. 18 Aug, 2020 1 commit
    • 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
  3. 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
  4. 09 Jun, 2020 1 commit
  5. 13 Nov, 2019 1 commit
  6. 13 May, 2019 1 commit
  7. 30 Nov, 2018 1 commit
  8. 09 May, 2018 1 commit
  9. 10 Nov, 2017 1 commit
  10. 09 May, 2017 1 commit
  11. 21 Apr, 2017 1 commit
  12. 30 Nov, 2016 1 commit
  13. 19 May, 2016 1 commit
  14. 04 Mar, 2016 1 commit
  15. 10 Nov, 2015 1 commit
  16. 21 Sep, 2015 1 commit
  17. 04 Sep, 2015 1 commit
  18. 05 May, 2015 1 commit
  19. 05 Nov, 2014 1 commit
  20. 29 Oct, 2014 1 commit
    • David Balch's avatar
      MDL-36874 mod_book: Add text navigation. · f4de8461
      David Balch authored
      Based on a patch by Matthew Cannings, this replaces Book's previous/next arrow
      image links with a choice of: no links, image links, or chapter title text links.
      f4de8461
  21. 09 May, 2014 1 commit
  22. 29 Jan, 2014 1 commit
  23. 05 Nov, 2013 1 commit
  24. 02 May, 2013 1 commit
  25. 30 Nov, 2012 1 commit
  26. 21 Oct, 2012 1 commit
    • Eloy Lafuente's avatar
      MDL-35297 book: replay some steps lost when book landed to core · 827b294c
      Eloy Lafuente authored
      This commit replays, conditionally, all the upgrade steps from
      MOODLE_19_STABLE to MOODLE_23_STABLE in the mod_book activity. That
      guarentees that any site using the mod_book before landing to core,
      no matter if it was the latest or an outdated one will upgrade
      perfectly to the expected current version.
      
      As a general rule, everytime one contrib plugin lands to core, its
      complete upgrade code must be kept, at least until the core version
      that introduced it, is out completely from the upgrade requirement
      conditions.
      
      In this case, with the missing upgrade code being added to 2.4, it
      will be safe to delete the upgrade steps once 2.5 (or upwards) become
      a requirement. Never always.
      827b294c
  27. 11 Oct, 2012 1 commit
  28. 07 Sep, 2012 1 commit
  29. 16 Aug, 2012 1 commit
  30. 18 Jun, 2012 1 commit
  31. 13 Jun, 2012 1 commit
  32. 27 May, 2012 1 commit
  33. 21 May, 2012 3 commits