Skip to content

The meaning of the labels

jantje edited this page Apr 25, 2016 · 4 revisions

We tag issues with labels and here we explain what those labels mean: Note that there is no process to give or take labels. As such the label reflects the perception of the label giver and not the community.

domains:

domain: configuration

Anything related with setting up the plugin. Be it internally or externally. Be it at startup or later.

domain: gui

Something visible that does not hurt the functionality.

domain: ino

Related to ino and pde files. People using Cpp files should not be impacted by these.

domain: other hardware

Related to boards that are not installed directly with the Arduino eclipse plugin.

domain: regression

This used to work but now it no longer does.

domain: scope

Something related to the scope.

domain: serial monitor

Something related to the serial monitor.

domain: upload

Something that makes the upload fail.

domain: version control

Something that impact the standard integrations with version controls. Typically this is files that should not change.

Status:

status: waiting for sponsor @ patreon

means: "It doesn't bother me, I don't think this affects enough people to bother the community, unless someone in the community steps forward as sponsor for this issue, this issue will not get attention from me."
This does not mean; that if you create a pull request it will not be accepted because of "no sponsorship".

To be entitled to be a sponsor you have to be a regular contributor or a patron sponsor of at least 1 dollar/month (exclusive VAT) on patreon. https://www.patreon.com/jantje?ty=h
Be honest to yourself. If you feel supporting this community with 1 dollar a month (exclusive VAT) is not worth it. Then this issue can not be important to you!! So why did you bother to create an issue in the first place?

status: Arduino IDE plugin incompatibility

The "sketch" "works" in arduino IDE but not in Eclipse.
I'm not sure this is really a "status" and not a "root cause".

status: duplicate

This issue is already tracked somewhere else. The issue should contain a link to the "duplicate" issue.

fixed in nightly

The issue is fixed but is not yet part of a release. Because it is not yet in a release the issue should be open.

Status: fixed in X.Y.Z

This issue is part of release X.Y.Z. As such this issue should be closed.

status: known limitation

We know this. We live with it. Probably the same as "status: waiting for sponsor @ patreon"

status: needs investigation

We are not yet sure what is going on and some data is available to look at.

status: no good solution found (yet)

We know what is going on here but we don't have a good solution to fix it.

status: rejected

We won't look at this.

status: usage error

The creator of the issue did something "wrong" or something "very exceptionally went wrong".

status: waiting for confirmation fix works

We have fixed something and it is in the nightly. So please tell us if you still have the problem.

status: waiting for implementation

We know what is the problem and how to fix it. It just needs to be done.

status: waiting for input

People who experience this issue are requested to provide more detailed information to progress the issue.

status: workaround documented

A work around is documented in the issue. This can take the pressure off.

importance

importance: board specific

This issue only impacts certain type of boards. For instance "due". The boards impacted should be identified in the issue.

importance: improvement request

This issue is a request to improve the plugin.

importance: internal stuff

This issue is something that has nothing to do with the usage of the plugin. It is about something the development community is experiencing. For instance build servers that are down.

importance: no user impact

This means: The plugin users are not impacted by this issue. For instance because it is a improvement request or because it is internal only or because it is just some extra data shown .....

importance: usability

This means: The usability of the plugin has decreased. In other words the plugin users are impacted.