Skip to content

RIOT's labeling system

Gaëtan Harter edited this page Oct 11, 2018 · 2 revisions

RIOT follows a labeling system roughly inspired by the labeling system of the Rust community. It is aiming make our labeling of issues and PRs more clearer and make it easier to filter through our vast amount of issues and PRs. At the moment there are 11 categories of labels:

  • Area labels state which area(s) of the RIOT's codebase the issue or PR relates to.
  • CI labels allow to control certain behavior of or give hints to the CI system.
  • Community labels solicit involvement by the community.
  • Discussion labels mark the status of an ongoing discussion within an issue or PR.
  • Impact labels mark the impact of a PR to the codebase. They also give a hint how careful the review for the change has to be.
  • OS labels mark issues or PRs that only relate to a specific host OS. As Linux is our default platform, all issues and PRs are implicitly relating to Linux, so no "OS: Linux" label exists.
  • Platform labels mark issues or PRs that only affect a specific platform or a set of platforms.
  • Process labels mark a state within the integration process of a PR
  • Reviewed labels mark the current state of the review of a PR. See the section on partial reviews in our maintainer guidelines for further details.
  • State labels mark the working condition or progression state of an issue or PR.
  • Type labels mark the type of issue or PR. Ideally an issue or PR has just one type.

All Labels and their description can be found on Github RIOT Labels page

Clone this wiki locally
You can’t perform that action at this time.