Labels

Pull request needs code review.

Pull request is reviewed well, but should not yet be merged.

Pull request requires no code review (e.g., a sub-repository hash update).

Pull request is in progress. No review needed at this stage.

Pull request did not receive any updates in a long time. No review needed at this stage. Close it.

Pull request is waiting for changes on the CI to complete tests before review/merge can begin.

Pull request requires author to sign off on CLA before review/merge can begin.

Pull request is reviewed and has significant issues which must be addressed.

Pull request has minor issues that must be addressed before merging.

Pull request has areas for improvement. The author need not address them before merging.

Pull request that reverts recent changes.

Pull request is reviewed well, but cannot be merged due to conflicts.

Pull request is reviewed well, but cannot be merged due to tests failing.

Pull request is already reviewed well in another branch.

Pull request is reviewed well.

Pull request is reviewed well and worth buying the author a beer.

Pull request is reviewed well and can not be compensated with any amount of beer in the galaxy ;)

Pull request should also be back-ported to the stable branch.

Changes should be mentioned in the release notes of the next minor version release.

This pull request blocks the next release from happening. Use only in extreme cases.

Issue can lead to a consensus failure.

The client panics and exits without proper error handling.

The client fails to follow expected, security-sensitive, behaviour.

The client fails to follow expected behavior.

The client behaves within expectations, however this “expected behaviour” itself is at issue.

Tests need fixing, improving or augmenting.

Documentation needs fixing, improving or augmenting.

Generic label for things that just have to get done but are no issues in first place.

Code needs refactoring.

An enhancement to provide a smaller (system load, memory, network or disk) footprint.