| [ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
| [ < Issues ] | [ Up : Issues ] | [ Bug Squad overview > ] | ||
8.1 Introduction to issues
Note: Unless otherwise specified, all the tasks in this chapter are “simple” tasks: they can be done by a normal user with nothing more than a web browser, email, and lilypond.
“Issues” isn’t just a politically-correct term for “bug”. We use the same tracker for feature requests, code TODOs and patches, so the term “bug” wouldn’t be accurate. Despite the difference between “issue” and “bug”, we call our team of contributors who organize issues the Bug Squad.
The Bug Squad is mainly composed of non-programmers – their job is to organize issues, not solve them. Their duties include removing false bug reports, ensuring that any real bug report contains enough information for developers, and checking that a developer’s fix actually resolves the problem.
New volunteers for the Bug Squad should contact the Bug Meister.
| [ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
| [ < Issues ] | [ Up : Issues ] | [ Bug Squad overview > ] | ||