Labels

• 0 - new

  Ticket is unclear on it's purpose or if it is valid or not
• 1 - triaged

  Tickets that are safe to pick up for contributing in terms of likeliness of being accepted
• 2 - pick next

  Used to mark issues which are next up in the queue to be worked on. The tag is non-binding
• 3 - in progress

  Someone is working on this ticket
• backport
• bug
• dependency-change
• discuss

  Tickets that need some discussion before proceeding. Not decided if it's a good idea.
• discuss-design

  Design discussion would be good
• failed

  Tickets that indicate a CI failure, likely a flakey test
• gardening
• good first issue
• hackathon

  Issues that could be tackled during a hackathon
• help wanted

  Issues that the core team will likely not have time to work on
• humongous
• large
• medium
• Merge After 2.6.0 Release
• needs-attention

  Indicates a PR validation failure (set by CI infrastructure)
• nice-to-have (low-prio)

  Tasks which make sense, however are not very high priority, feel free to help out!
• obsolete – reopen if necessary

  Ticket closed as currently obsolete, reopen if discussion still relevant
• reviewed

  Ready to merge from review perspetive, but awaiting some additional action (e.g. order of merges)
• small
• stashed PR
• t:build
• t:camel
• t:cluster
• t:cluster-sharding
• t:cluster-tools
• t:cluster:dc