issue labeling scheme
Each PR and Issue is labeled along five "dimensions", each with its own color family:
- C: Component
- I: Interface
- P: Progress
- S: Severity
- T: Type
Documentation- Documentation updates, fixes, ...
Infrastructure- changes in the build system or CI scripts
Installation
Interpreter- changes in the SLI iterpreter
Kernel- changes in the NEST kernel
Model- new or modified neuron or synapse models
PyNEST- changes in the high level python interface of NEST
Behaviour changes- changes to the semantics of parameters or return values, while keeping the same API
- changes in the effect of a method
External API- change that requires users of NEST to change their code accordingly
Internal API- change that modifies the calls to functions not usually handled by users
- NEST developers need to be aware about the new structure/parameters/methods...
No breaking change- no change to any API that would break existing code
- anything that compiled before should still compile afterwards
User Interface- changes to the user interface
Blocked
In progress
Pending
PR Created
Reminder
Critical- Critical, bugs that need to be fixed asap.
High- default priority for bugs, important enhancements
Low- default priority for everything but bugs, bugs that appear in very corner cases
Bug
Discussion- Ideas, Wishlist, everything that needs comments from the community or has to be condensed to a more concrete plan
External bug
Maintenance
