Triaging

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.

Initial status and type
New issues get and are also given one of:
 * - the issue is a well defined bug report
 * - the issue is a question or support request, not a bug
 * - the issue describes a missing feature

Device category
If the issue affects devices, a device-category label for the highest affected device category is added.


 * - affects at least one device in the main category
 * - affects at least one device in the community category
 * - affects at least one device in the testing category

For devices in main and community categories, we also have one issue label per device, for example. These get added as well.

Status change
During the lifetime of the issue, the status may change:
 * - issue has been confirmed (bug reproduced or it has been agreed upon implementing a feature request)
 * - issue is blocked because the reporter needs to provide more information
 * - the bug report describes intended behaviour or for some reason we won't fix this
 * - this issue describes a bug in an upstream project.
 * - this is not a valid issue
 * - this is a duplicate of an existing issue.
 * - the issue has been fixed!

Upstream issue
If the issue reported is an upstream bug, it doesn't always make sense to close it immediately. If having a local issue to track it adds value, for example if this is a very important bug and we need to know when it is fixed in postmarketOS, is applied but the issue is kept open. Once it's fixed upstream AND fixed in postmarketOS, the gets applied and the issue gets closed.

On the other hand, if it it doesn't add value to keep the bug around in postmarketOS, it should be closed after applying.

In any case, a link to the upstream issue should be added to the issue - preferably edited into the top post so it's immediately visible when reading the issue.

Merge Requests
Similarly to issues, MRs should be assigned of either  or. As well as appropriate device and.

labels only necessary for MRs that are closed instead of merged, only makes sense here.