Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Field Guide to Callisto Bugs"
(→Hot Spots for this Milestone) |
|||
| Line 10: | Line 10: | ||
| − | There | + | There is [[http://www.eclipse.org/projects/callisto-files/callisto-bug-contest.php a contest for the best reports]]. Great bug reporters: |
* Get Action (by understanding what action is required and facilitating that.) | * Get Action (by understanding what action is required and facilitating that.) | ||
* Max Value (by recognizing where and how to find the bugs that really matter.) | * Max Value (by recognizing where and how to find the bugs that really matter.) | ||
Revision as of 18:07, 11 March 2006
This page will help Callisto bug hunters and bug fixers coordinate their efforts. The ways we make the best use of everyone's time will evolve with each milestone leading to the simultainous release. Consult this page to get and give tips on finding bugs with value and producing reports with action.
Hot Spots for this Milestone
- This is a big one for the update manager. Look for glitches there, at the update site, and its mirrors.
Tips for Writing Winning Bug Reports
There is [a contest for the best reports]. Great bug reporters:
- Get Action (by understanding what action is required and facilitating that.)
- Max Value (by recognizing where and how to find the bugs that really matter.)