github-issue-labels 1.3 KB

1234567891011121314151617181920212223242526272829
  1. Explanations for possibly mysterious lables used on Optiboot github "issues."
  2. Component-Docs - requires a fix in the documentation only
  3. Component-Makefiles - requires a change to the makefiles only
  4. Component-Scripts - changes to the scripts only
  5. Discussion - an "issue" that has significant "discussion" involved; may not be an actual bug.
  6. Duplicate
  7. help wanted - "official maintainers" don't have the parts or the interest. A request for someone in the community to provide a patch/pull request/etc.
  8. Invalid - the bug is reported in error, or determined not to exist.
  9. Maintainability - affects the ease of maintenance of the program.
  10. Not-our-issue - the actual problem is determined to lie outside of optiboot itself.
  11. OpSys-Linux
  12. OpSys-OSX
  13. OpSys-Windows
  14. Partly Done - come code has been added/merged, but there is more to do.
  15. Priority-Critical
  16. Priority-High
  17. Priority-Low
  18. Priority-Medium
  19. Question - more of a
  20. Regression - something that used to work correctly has broken
  21. Superseded - was a bug at one time, but is no longer present because of other changes.
  22. Type-Defect
  23. Type-Enhancement
  24. Type-newChip - request for a new chip; usually involves Makefile and pin_defs.h, but not actual program logic.
  25. Type-Other
  26. Type-Patch
  27. wontfix - describes a real problem that can't be fixed, or won't be fixed because we think it is outside the scope of Optiboot.