1. 23 Oct, 2018 2 commits
  2. 22 Oct, 2018 1 commit
  3. 18 Oct, 2018 2 commits
  4. 02 Oct, 2018 1 commit
  5. 26 Sep, 2018 2 commits
  6. 20 Sep, 2018 7 commits
  7. 31 Aug, 2018 2 commits
  8. 29 Aug, 2018 1 commit
  9. 27 Aug, 2018 2 commits
  10. 09 Aug, 2018 2 commits
  11. 16 Jul, 2018 1 commit
  12. 03 Jul, 2018 1 commit
  13. 29 May, 2018 3 commits
  14. 28 May, 2018 1 commit
  15. 10 May, 2018 2 commits
  16. 24 Apr, 2018 1 commit
  17. 29 Mar, 2018 3 commits
  18. 21 Mar, 2018 2 commits
  19. 13 Mar, 2018 1 commit
  20. 02 Feb, 2018 1 commit
    • totten's avatar
      extdir - When filtering by version, support forward-compatibility among 5.x · 0dbac544
      totten authored
      Comments:
      
      * For versions <=4, compatibility tests are exact.  Thus, a site running
        '4.6.20' would only see extensions that were tagged `<ver>4.6</ver>`
        but not `<ver>4.5</ver>`. This preserves existing behavior.
      * For version 5, forward-compatibility is assumed.  Thus, a site running
        '5.1.0' would see extensions that were tagged as '<ver>5.0</ver>' or
        '<ver>5.1</ver>'.  Also, because `5.{$y}` is really a continuation of
        `4.7.{$z}`, we include extensions from "4.7".
      * This assumes that we prefill the list of taxonomy terms (e.g.  "CiviCRM
        5.0" through "CiviCRM 5.36").
      
      See also: https://lab.civicrm.org/development-team/Release-Management/issues/1
      0dbac544
  21. 14 Dec, 2017 1 commit
  22. 08 Dec, 2017 1 commit