Labels

• effort: high

  The issue will probably take a single contributor several days of work to resolve.
• effort: low

  The issue will probably take a single contributor no more than one day of work to resolve.
• effort: moderate

  The issue will probably take a single contributor one or two days of work to resolve.
• effort: very high

  The issue will probably take a single contributor more than a week of work to resolve.
• issue: duplicate

  The issue was closed because it's a duplicate of another issue.
• issue: invalid

  The issue was closed because it's inapplicable or doesn't make sense.
• issue: question

  The issue is a question, and it should be closed after the question is answered.
• issue: wontfix

  The issue was closed because the relevant changes are not justifiable.
• meta: blocked

  The issue cannot be resolved right now, but it should be in the future.
• meta: good first issue

  The issue is especially suitable for first-time contributors.
• meta: needs work

  The issue cannot progress until additional work is done.
• meta: next release

  The issue must be resolved before the next version can be released.
• priority: critical

  The issue must be resolved as soon as possible.
• priority: high

  The issue substantially impedes people's ability to use the software.
• priority: low

  The issue has only a small impact on people using the software.
• priority: medium

  The issue makes it more difficult for people to use the software.
• priority: trivial

  The issue has very little impact on people using the software.
• type: bug

  The issue involves incorrect or unexpected behavior.
• type: code quality

  The issue involves code organization and readability.
• type: documentation

  This issue pertains to the clarity or exhaustiveness of documentation.
• type: feature

  The issue involves adding new or extended behavior to the software.
• type: integration

  The issue involves interactions with other software.
• type: optimization

  The issue involves making existing functionality more performant.
• type: polish

  The issue involves making existing functionality more usable.
• type: security

  The issue pertains to possible security threats and vulnerabilities.
• type: stability

  The issue pertains to automated testing or other tools for verifying code correctness.