Platform UI Bugs

Logging

We use component area tags in square brackets in the bug Summary. These tags denote the area in Platform UI where the bug exists. The tags facilitate querying of all bugs in a certain component category. Different committers own different components.

When logging a bug, you can use these tags to help the person triaging to better understand the bug and to know who to assign the bug to.

Triage

• one member of the team acts as "triage monkey"
• "triage monkey" assigns bug to the appropriate owner
• you can use the greasemonkey script to automate category and ownership assignment
• owner examines bug and applies categorization

Categorization

Real

The bug is real and is one we intend on fixing in the milestone specific. Although we cannot promise to address it in this timeframe this is our intention.

Status: ASSIGNED
Milestone: something reasonable

Real No Time

The bug is real but we do not have the time to address it. We would entertain patches for these issues.

Status: ASSIGNED
Milestone: no milestone
Keywords: helpwanted if appropriate

Real Not A Priority

The bug is real but we do not feel it's that important. We would entertain patches for these issues.

Status: ASSIGNED
Keywords: helpwanted if appropriate
Priority: P5

Not Real

The bug is not valid. We will not address it further. If it's a bug regarding established behaviour we do not wish to change mark as WONTFIX. If it's simply not a problem as described in the report use INVALID.

Status: WONTFIX or INVALID

Accepting Patches From The Community

The following steps should be taken when committing patches from members of the community who are not committers on the Eclipse top-level project.

1. examine the patch and apply if it's deemed acceptable
2. ensure that the bug is assigned to yourself
3. ensure that the bug has the "contributed" keyword
4. mark the bug as fixed and include in the comment "patch applied"