Skip to content
Snippets Groups Projects
  1. Nov 27, 2024
  2. Nov 20, 2024
  3. Nov 19, 2024
  4. Nov 06, 2024
  5. Sep 01, 2024
  6. Aug 27, 2024
  7. Aug 20, 2024
  8. Aug 06, 2024
  9. Jul 31, 2024
  10. Jul 24, 2024
  11. Jul 03, 2024
  12. Jun 19, 2024
    • Casey's avatar
      testing/device-postmarketos-trailblazer (MR 4967) · ca9a26cb
      Casey authored
      
      trailblazer is a bleeding edge, unstable target for EFI capable ARM64
      devices. It runs linux-next and should otherwise be adjusted to support
      as many devices as possible.
      
      The goal of trailblazer is to motivate more upstream kernel development by
      providing a tighter feedback loop (patches land in -next weeks before they
      make it into mainline or stable), as well as encouraging more generic
      solutions to the device specific hacks we have in userspace.
      
      On supported devices, trailblazer should reflect the current state of
      upstream. It allows users to easily appreciate what feature are
      unavailable, and more importantly appreciate when a new feature does get
      added upstream.
      
      Due to the instability of linux-next, the plan is to have BPO build
      trailblazer images nightly, so if next breaks then the images should
      only be broken for a day.
      
      Signed-off-by: default avatarCaleb Connolly <caleb@postmarketos.org>
      ca9a26cb
    • Casey's avatar
      testing/linux-next: new aport (MR 4967) · 18462c56
      Casey authored
      
      Introduce a linux-next kernel with postmarketOS configs and some
      additional device specific configs enabled.
      
      This kernel package will be updated daily to the latest -next tag.
      breakages expected. It is designed to be used in tandem with a generic
      ARM64 device package to provide a bleeding edge option for those with
      EFI capable bootloaders.
      
      Signed-off-by: default avatarCaleb Connolly <caleb@postmarketos.org>
      18462c56
  13. Jun 06, 2024
  14. May 27, 2024
  15. May 22, 2024
  16. May 20, 2024
  17. May 19, 2024
  18. May 17, 2024
  19. May 02, 2024
  20. Apr 20, 2024
  21. Apr 11, 2024
  22. Apr 02, 2024
  23. Mar 31, 2024
  24. Mar 25, 2024
  25. Mar 19, 2024
  26. Mar 18, 2024
    • Oliver Smith's avatar
      CI: add more tests for CODEOWNERS (MR 4940) · 2d0a7aa6
      Oliver Smith authored
      * Parse the file in python and ensure it is ordered alphabetically
      * Ensure that we have at least as many gitlab nicknames in CODEOWNERS,
        as there are listed maintainers in main and community devices. This
        should help with enforcing that every maintainer is also listed in
        CODEOWNERS, so they can be easily pinged via their gitlab nickname if
        something for the device they maintain is happening.
      
      [ci:skip-build]: already built successfully in CI
      2d0a7aa6
    • Oliver Smith's avatar
      CODEOWNERS: add maintainers from APKBUILDs (MR 4940) · 8bf7a0f6
      Oliver Smith authored
      Sometimes we need to figure out the gitlab nicknames of maintainers and
      co-maintainers as listed in the APKBUILDs, e.g. when a specific issue
      appears that only happens with a given device. Or if we want to ping
      all device maintainers in the testing phase for the new release.
      
      So far it has been a very tiresome, manual process to figure out gitlab
      nicknames from the maintainers in the APKBUILDs (involving git log
      --follow and opening merge requests in browsers...). After some
      discussion we figured it would be good to store it in the CODEOWNERS
      file.
      
      This also has the nice side-effect that maintainers get notifications if
      the APKBUILDs they maintain get changed.
      8bf7a0f6
  27. Mar 17, 2024
  28. Feb 11, 2024
Loading