1. 31 Oct, 2016 2 commits
  2. 27 Oct, 2016 2 commits
  3. 21 Oct, 2016 1 commit
  4. 25 Sep, 2016 2 commits
  5. 15 Sep, 2016 2 commits
  6. 13 Sep, 2016 1 commit
  7. 06 Sep, 2016 2 commits
  8. 04 Sep, 2016 2 commits
  9. 02 Sep, 2016 1 commit
  10. 29 Aug, 2016 1 commit
  11. 28 Aug, 2016 1 commit
  12. 26 Aug, 2016 2 commits
  13. 23 Aug, 2016 1 commit
  14. 22 Aug, 2016 1 commit
  15. 08 Jun, 2016 2 commits
  16. 07 Jun, 2016 3 commits
  17. 30 May, 2016 1 commit
  18. 22 May, 2016 1 commit
    • Son Nguyen's avatar
      Add more translations from Launchpad.net · 45658b86
      Son Nguyen authored
      - Chinese Traditional - zh_CN
      - Indonesia - id
      - Estonia - et
      - Kannada - kn
      - Mongola - mn
      - Persian - fa
      - Polish - pl
      - Romanian - ro
      - Serbian - sr
      - Thai - th
      - Turkish - tr
      - Ukrainian - uk
      - Hungarian - hu
      
      Change-Id: I31d85f9525762d724e8dd426dc4a5ba08e7dd285
      45658b86
  19. 02 May, 2016 1 commit
  20. 11 Apr, 2016 5 commits
  21. 10 Mar, 2016 3 commits
  22. 09 Mar, 2016 2 commits
  23. 08 Mar, 2016 1 commit
    • Aaron Wells's avatar
      Prevent automatic running of code submitted by untrusted Gerrit users · e1ce4af9
      Aaron Wells authored
      For security reasons, it's unwise to allow running of arbitrary code
      uploaded my members of the general public. This test should limit
      automated test running, to code uploaded by users who have been
      manually added to the "Mahara Testers" or "Mahara Reviewers" groups.
      (And/or code that has a +2 code review)
      
      The check is against the code *uploader*, not the Gerrit change *owner*,
      so if a patch is rebased by a trusted user, it will trigger automatic
      code execution.
      e1ce4af9