Initiatives and goals across modules and releases. Epics are scoped, prioritized (among other initiatives) and doable. Epics are adviced to follow a Minimum Viable Change approach.

Refactoring, technological debt, etc.

An intermittently reproducible/flaky issue or test failure

Issues which involve deprecating existing API, which must be done before API freeze (see https://wiki.gnome.org/ReleasePlanning/Freezes)

Issues which require an API break in order to be fixed, and hence cannot be fixed until the next major release of GLib

Issues with the CI infrastructure or setup

Internationalisation or localisation issues

Issues which introduce new API to GLib, which must land outside of the next API freeze (see https://wiki.gnome.org/ReleasePlanning/Freezes)

Issues where a test has failed

Merge requests where a unit test needs to be added before it can be merged

Human-perceptible delays in response time to user actions, or issues related to the excessive use of system resources like CPU, I/O, GPU, etc.

Initiatives#42

Initiatives#43

Initiatives#44