Prioritized Labels
  • pri::p1
    Top priority, MR fixes critical problem affecting existing installations and must be reviewed, tested and merged as soon as possible
    • Project label
  • pri::p2
    High priority. MR fixes bug affecting existing installations. Though the workaround exists, MR should be processed in priority order
    • Project label
  • pri::p3
    Normal priority. MR should be processed in usual order
    • Project label
  • pri::p4
    Low priority. Insignificant cosmetic changes which can be processed in background order
    • Project label
  • comp::trivial
    Trivial changes which can take up to 5 minutes to review and up to 15 minutes to test
    • Project label
  • comp::low
    Changes which can take up to 1 hour to test
    • Project label
  • comp::high
    Most complicated changes
    • Project label
  • comp::medium
    Changes which can take up to 1 day to test
    • Project label
  • kind::bug
    Bugfix
    • Project label
  • kind::cleanup
    Code cleanup. Non-functional changes not affecting existing behavior, like code formatting
    • Project label
  • kind::feature
    functional changes improving existing feature or adding new one
    • Project label
  • kind::improvement
    Non-functional changes, including code and infrastructure optimization, requirements updates or additional documentation
    • Project label
  • Other Labels
  • arch
    • Project label
  • backend
    • Project label
  • backport
    • Project label
  • beef
    • Project label
  • BI
    • Project label
  • Bug
    • Group label
  • card
    • Project label
  • cleanup
    • Project label
  • clickhouse
    • Project label
  • cm
    • Project label
  • collections
    • Project label
  • confdb
    • Project label
  • core
    • Project label
  • deploy
    • Project label
  • discovery
    • Project label
  • discussion
    • Project label
  • dns
    • Project label
  • documentation
    • Project label
  • Doing
    • Project label
  • epic
    • Project label