Pull request that is backported from a more recent version.
Code refactoring that does not change the behavior.
Documentation such as function documentations, comments and tutorials.
Implementation that does not break interfaces.
Example, e.g. the MNIST example.
Implementation that introduces new interfaces.
Ticket that do not fall into any other cat-label.
Performance in terms of speed or memory consumption.
Long running PR for ChainerX task board
Contribution is welcomed. If a ticket has this label, anyone is welcomed to work on it.
Related to Computer Vision.
Change that disrupts backward compatibility.
Pull-request is being worked on to address the labeled ticket.
High priority. Urgent and needs to be worked on as soon as possible.
Low priority. Nice-to-have.
Medium priority. Should be worked on but does not require immediate action.
Pull request that is mandatory for a release.
Included in future roadmap.
State indicating that response is needed from contributors, often authors of pull request.
State indicating that a member from the core teams need to take action.