Skip to content

Prioritized labels 0

Drag to reorder prioritized labels and change their relative priority.

Other labels 58

  • 0. Awaiting other issue
    GNOME / evolution
    Set when the issue is waiting for a fix from another issue; which it is should be part of the comments
  • 1. Bug
    GNOME
    Problems, incorrect behavior or appearance
  • 1. Cleanup
    GNOME
    Refactoring, technological debt, etc.
  • 1. Crash
    GNOME
    The issue is a crash in the software
  • Issues that propose improvements to existing features
  • 1. Epic
    GNOME
    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.
  • 1. Feature
    GNOME
    New features or capabilities to be added
  • 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.
  • Issue is an unintended break of previous working behavior
  • 1. Security
    GNOME
    Security, privacy or safety issues
  • This merge request has been accepted but should only be merged once the module emerges from code freeze (see https://wiki.gnome.org/ReleasePlanning/Freezes)
  • Needs an acceptable design solution to be identified
  • The issue needs more diagnosis to triage
  • Needs additional information to be diagnosed and/or resolved
  • 2. RFC
    GNOME
    Request For Comments and discussions from developers
  • Issue describes something that does not need to be changed
  • Issue is too generic or is not actionable
  • 3. Not GNOME
    GNOME
    Issue belongs to non-GNOME software, or is not caused by upstream/vanilla GNOME. It maybe another component of the operating system, or caused by modifications made by downstream distributors.
  • Requested changes don't align with current technologies, designs or plans