Difference between revisions of "Every Detail Matters/Great Fix"
(→Anatomy of a Great Bug) |
|||
Line 1: | Line 1: | ||
{{Warning|Work in progress}} | {{Warning|Work in progress}} | ||
− | What constitutes a great | + | What constitutes a great fix? Take a look at [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=greatbug&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= the list] and see for yourself some examples of what the developers think are great fixes. Roughly speaking, we’re looking for bugs that affect one of the [[Mars]] projects that has a significant impact on the community (e.g. something in the Platform that impacts many extenders, or something to do with the integration of two or more different projects). |
What's at stake? Why the future of the developer's platform, of course! More seriously, there will be prizes. More later. | What's at stake? Why the future of the developer's platform, of course! More seriously, there will be prizes. More later. | ||
Line 15: | Line 15: | ||
* Host regular (monthly) "bug day" leading up to the Mars release | * Host regular (monthly) "bug day" leading up to the Mars release | ||
− | * Project committers will mark bugs they deem worthy with the " | + | * Project committers will mark bugs they deem worthy with the "greatfix" keyword |
− | * "Developer Platform Vision" committee will rank the " | + | * "Developer Platform Vision" committee will rank the "greatfix" bugs |
* Winners will be announced on Mars GA day! | * Winners will be announced on Mars GA day! | ||
+ | * Prizes are awarded to both the contributor and the committer (accepting fixes is hard work too!) |
Revision as of 13:10, 14 January 2015
What constitutes a great fix? Take a look at the list and see for yourself some examples of what the developers think are great fixes. Roughly speaking, we’re looking for bugs that affect one of the Mars projects that has a significant impact on the community (e.g. something in the Platform that impacts many extenders, or something to do with the integration of two or more different projects).
What's at stake? Why the future of the developer's platform, of course! More seriously, there will be prizes. More later.
Anatomy of a Great Fix
- Detailed discussion via bug comments
- Code contribution via the mechanism described by the project (e.g. Gerrit)
- Code conforms to the the style prescribed by the project
- Updates and additions to unit tests included
Process
- Host regular (monthly) "bug day" leading up to the Mars release
- Project committers will mark bugs they deem worthy with the "greatfix" keyword
- "Developer Platform Vision" committee will rank the "greatfix" bugs
- Winners will be announced on Mars GA day!
- Prizes are awarded to both the contributor and the committer (accepting fixes is hard work too!)