1. 29 Mar, 2018 1 commit
  2. 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
  3. 16 Nov, 2017 1 commit
  4. 01 Nov, 2017 1 commit
  5. 26 Oct, 2017 1 commit
  6. 25 Oct, 2017 1 commit
  7. 18 May, 2017 2 commits
  8. 17 May, 2017 1 commit
  9. 14 May, 2017 3 commits
  10. 18 Apr, 2017 1 commit
  11. 15 Mar, 2017 2 commits
  12. 18 Jan, 2017 1 commit
  13. 17 Jan, 2017 3 commits
  14. 29 Dec, 2016 1 commit
  15. 27 Dec, 2016 1 commit
  16. 14 Dec, 2016 1 commit
    • Stoob's avatar
      change group number · bd7acb1a
      Stoob authored
      According to josh, group #131 is no longer in use for determining if a contact is a contributor or active contributor.  Instead group #487 has been used, which includes 6 child groups.  I'm changing the group id# so the link should appear (hopefully) on contributor pages such as https://civicrm.org/user/####/edit
      bd7acb1a
  17. 02 Dec, 2016 1 commit
  18. 30 Nov, 2016 1 commit