1. 29 May, 2021 1 commit
  2. 21 May, 2021 1 commit
  3. 19 May, 2021 1 commit
  4. 05 May, 2021 1 commit
  5. 30 Apr, 2021 1 commit
  6. 29 Apr, 2021 1 commit
  7. 27 Apr, 2021 1 commit
  8. 19 Apr, 2021 2 commits
  9. 15 Apr, 2021 2 commits
  10. 14 Apr, 2021 1 commit
  11. 08 Apr, 2021 1 commit
  12. 04 Apr, 2021 1 commit
  13. 26 Mar, 2021 1 commit
  14. 25 Mar, 2021 2 commits
  15. 12 Mar, 2021 1 commit
  16. 03 Mar, 2021 1 commit
  17. 01 Mar, 2021 1 commit
  18. 27 Feb, 2021 1 commit
  19. 17 Feb, 2021 1 commit
  20. 05 Feb, 2021 2 commits
  21. 03 Feb, 2021 1 commit
  22. 29 Jan, 2021 1 commit
  23. 04 Jan, 2021 1 commit
  24. 16 Nov, 2020 2 commits
  25. 03 Nov, 2020 1 commit
  26. 02 Nov, 2020 1 commit
  27. 29 Oct, 2020 1 commit
  28. 28 Oct, 2020 2 commits
  29. 29 Sep, 2020 1 commit
  30. 18 Sep, 2020 1 commit
  31. 31 Aug, 2020 1 commit
    • Lars Rickard Strom's avatar
      Fixing check for compatibility between release and jet collection name · 6a4a3f09
      Lars Rickard Strom authored
      The compatibility check failed for release numbers above 99 due to
      simple string comparison (did not properly compare two-digits release
      numbers with three-digits needed for releases 21.2.100 and above).
      This caused runtime error incorrectly stating that the configured
      release was older than 21.2.72.0. This patch corrects for that by
      instead comparing the release numbers as integers. An informative
      message stating the release number read from the sample meta data
      was also added to the INFO output.
      6a4a3f09
  32. 28 Aug, 2020 1 commit
  33. 21 Aug, 2020 1 commit
  34. 18 Aug, 2020 1 commit