1. 24 Mar, 2020 4 commits
  2. 12 Mar, 2020 1 commit
  3. 10 Mar, 2020 3 commits
  4. 09 Mar, 2020 5 commits
  5. 06 Mar, 2020 3 commits
  6. 04 Mar, 2020 1 commit
  7. 17 Feb, 2020 1 commit
  8. 13 Feb, 2020 1 commit
  9. 08 Feb, 2020 2 commits
    • Martyn Welch's avatar
      Remove out-of-date release information · 3b883be7
      Martyn Welch authored
      We have lots of duplicated and out-of-date information on various Apertis
      sites. Remove the out-of-date release information from apertis designs and
      for now point at the ci-package-builder documentation.
      Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
      3b883be7
    • Martyn Welch's avatar
      Update release guidance · 76c95647
      Martyn Welch authored
      The guide for issuing a release has got out of date. The CI automation
      will now create the required tags for us - we shouldn't be creating tags.
      
      Additionally we should no longer be pushing the release directly and we've
      also started using `gbp dch` to formulate the contents of the changelog
      entry as submitting a merge request as direct pushes have been disabled to
      ensure all changes are made correctly.
      Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
      76c95647
  10. 04 Feb, 2020 1 commit
    • Emanuele Aina's avatar
      Merge branch 'packaging/apertis/v2021dev1' into apertis/v2021dev1 · 591c828c
      Emanuele Aina authored
      While converting the package to the new GitLab-to-OBS pipeline the project
      was mistakenly forked under `pkg/` rather than transferred and now the
      repositories went out of sync.
      
      Fold the changes back so we can replace the forked repository with the
      original one.
      
      * packaging/apertis/v2021dev1:
        Releasing apertis version 1.2020.1.
        gitlab-ci: Link to the Apertis GitLab CI pipeline definition
      591c828c
  11. 03 Feb, 2020 2 commits
  12. 30 Jan, 2020 2 commits
  13. 29 Jan, 2020 1 commit
  14. 28 Jan, 2020 2 commits
  15. 26 Jan, 2020 1 commit
  16. 24 Jan, 2020 1 commit
  17. 23 Jan, 2020 1 commit
  18. 17 Jan, 2020 1 commit
  19. 16 Jan, 2020 3 commits
  20. 15 Jan, 2020 2 commits
  21. 08 Jan, 2020 1 commit
  22. 01 Jan, 2020 1 commit
    • Emanuele Aina's avatar
      hotdoc-html-2-pdf: Set up fonts to better handle unicode data · 7da77bb9
      Emanuele Aina authored
      It's 2019 and *TeX still lacks proper glyph fallback, so we get the following
      errors on `make pdf`:
      
          ./hotdoc-html-2-pdf build/html/appdev-debugging.html build/pdf/appdev-debugging.pdf --remote-prefix "https://developer.apertis.org" --line-numbers
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          ./hotdoc-html-2-pdf build/html/programming-guide-tooling.html build/pdf/programming-guide-tooling.pdf --remote-prefix "https://developer.apertis.org" --line-numbers
          [WARNING] Missing character: There is no 李 in font [lmmono10-regular]:!
          [WARNING] Missing character: There is no 健 in font [lmmono10-regular]:!
          [WARNING] Missing character: There is no 秋 in font [lmmono10-regular]:!
          ./hotdoc-html-2-pdf build/html/vm-config.html build/pdf/vm-config.pdf --remote-prefix "https://developer.apertis.org" --line-numbers
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          ./hotdoc-html-2-pdf build/html/vm-management.html build/pdf/vm-management.pdf --remote-prefix "https://developer.apertis.org" --line-numbers
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          ./hotdoc-html-2-pdf build/html/vm-setup.html build/pdf/vm-setup.pdf --remote-prefix "https://developer.apertis.org" --line-numbers
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
          [WARNING] Missing character: There is no ▸ in font [lmmono10-regular]:!
      
      Address those by:
      * setting up a CJK font so we don't erase team members
      * setting up a monospace font which has large Unicode coverage without
        requiring fallbacks, so a `▸` in a code snippets doesn't end up in a
        unrendered character
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      7da77bb9