Add Label section to CONTRIBUTING

[4-20ma]

ModbusMaster version

0.11.0

Arduino IDE version

any

Arduino Hardware

any

Platform Details

any

---

Feature Request

Narrative:

As a maintainer
I want to apply a structured approach to assigning issue labels
So that they are consistent over time

As a contributor or project user
I want to know how/why labels are assigned
So that I understand...
  issue status and how it's assigned,
  issue priority and how it's assigned, and
  issue type and how it's assigned

Implementation notes

Priority

• Priority will generally start as Low and will be upgraded to Medium, High, or Critical, depending on the severity of the issue

Status

• Abandoned: issue closed due to inactivity or item that will not be fixed
• Blocked: issue or PR that will not be fixed (include explanation in issue/PR)
• In Progress: issue has been assigned and is actively being addressed; label issue On Hold with comments if there will be a significant delay
• Maintainer Review Needed: last step prior to merge; PR passes continuous integration tests and are able to be cleanly merged - awaiting review for style, code cleanliness, etc.
• On Hold: provide various reasons an issue or PR might be on hold
• Pending Contributor Response: closed after 14 days of inactivity (label Abandoned at closure)

Type

• Bug: requires clear test case and be reproducible
• Differentiate between enhancement, feature request, maintenance (with examples)
• Feature requests require well-written, clear user story
• Question - self explanatory