Jump to content

Triaging

From postmarketOS Wiki
Revision as of 19:11, 16 October 2022 by Caleb (talk | contribs) (Created page with "This page explains the triage process for issues and merge requests. It's written for pmaports and pmbootstrap but also applies to other postmarketOS maintained repositories....")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page explains the triage process for issues and merge requests. It's written for pmaports and pmbootstrap but also applies to other postmarketOS maintained repositories.


🚧 This page is a work-in-progress. Some information contained within may be inaccurate or incomplete.
In particular: Missing issue lifespan and MRs

Issues

New issues get the status::reported label and are also given one of:

  • type::bug - the issue is a well defined bug report
  • type::support - the issue is a question or support request, not a bug
  • type::feature - the issue describes a missing feature

If the issue affects devices, the label for the affected device[s] are added, as well as a device-category label for the highest priority device. e.g. if it affects a main and community device, the device-category::main label is added.