Bibliography
[Anvik et al. 2005] Coping with an open bug repository. Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange: 35‒39. .
[Bettenburg et al. 2008a] . What Makes a Good Bug Report? . Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering: 308‒318.
[Bettenburg et al. 2008b] . Duplicate Bug Reports Considered Harmful...Really? . Proceedings of the 24th International Conference on Software Maintenance .
[Breu et al. 2010] Proceedings of the Conference on Computer Supported Cooperative Work. Information Needs in Bug Reports: Improving Cooperation Between Developers and Users . Proceedings of the 2010 ACM Conference on Computer Supported Cooperative Work: 301‒310.
[Cherry and Vesterman 1981] Writing Tools—The STYLE and DICTION Programs. Computer Science Technical Report No. 91, Bell Laboratories, Murray Hill, NJ . .
[Goldberg 2010] Bug Writing Guidelines. https://developer.mozilla.org/en/Bug_writing_guidelines .
[Guo et al. 2010] Characterizing and ...
Get Making Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.