1. 13 Apr, 2022 1 commit
  2. 12 Jan, 2022 1 commit
  3. 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 o...
      fbb07675
  4. 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
  5. 09 Jun, 2020 1 commit
  6. 13 Nov, 2019 1 commit
  7. 04 Oct, 2019 1 commit
  8. 02 Oct, 2019 1 commit
  9. 09 Sep, 2019 1 commit
  10. 12 Jul, 2019 3 commits
  11. 07 Jun, 2019 1 commit
  12. 13 May, 2019 1 commit
  13. 11 Apr, 2019 1 commit
  14. 08 Mar, 2019 1 commit
  15. 26 Feb, 2019 1 commit
  16. 30 Nov, 2018 1 commit
  17. 09 May, 2018 1 commit
  18. 02 May, 2018 1 commit
  19. 10 Nov, 2017 1 commit
  20. 13 Oct, 2017 1 commit
    • David Monllaó's avatar
      MDL-59988 analytics: Files marked as used only if valid · 325b3bdd
      David Monllaó authored
      - Basic unit test for minimum machine learning backends requirements
      - Warning return messages now include not enough data
      - Clear models when the predictions processor is changed
      - Refined the name of a couple of constants / methods
      325b3bdd
  21. 03 Oct, 2017 1 commit
  22. 07 Sep, 2017 1 commit
  23. 05 Sep, 2017 1 commit
  24. 25 Aug, 2017 2 commits
    • David Monllaó's avatar
    • David Monllaó's avatar
      MDL-59265 analytics: Rename machine learning backend method · 5c5cb3ee
      David Monllaó authored
      - Method names renamed to avoid interface changes once
        we support regression and unsupervised learning
      - Adding regressor interface even if not implemente
      - predictor interface comments expanded
      - Differentiate model's required accuracy from predictions quality
      - Add missing get_callback_boundary call
      - Updated datasets' metadata to allow 3rd parties to code
        regressors themselves
      - Add missing option to exception message
      - Include target data into the dataset regardless of being a prediction
        dataset or a training dataset
      - Explicit in_array and array_search non-strict calls
      - Overwrite discrete should_be_displayed implementation with the binary one
      - Overwrite no_teacher get_display_value as it would otherwise look
        wrong
      - Other minor fixes
      5c5cb3ee
  25. 24 Jul, 2017 8 commits