Once the bug report is filed, contributors and committers work on it, including updates to bug status. All users may contribute to the discussion by adding comments (but typically not change the status fields). The Eclipse Process Guidelines contain some good [http://www.eclipse.org/projects/dev_process/bugzilla-use.php information and a handy diagram] for understanding the lifecycle of an issue in Bugzilla.

+

+

=== How bugs are ASSIGNED ===

+

# All bug should be created with the "Assigned To" field set to dd.general-inbox@eclipse.org. This allows everyone watching the list to observe bug activity.

+

#* Component owner, which is normally the leader of the sub-project owns the component, confirms that the bug is valid and assigns it to a committer or contributor.

+

#* Alternatively, if a contributor created the bug for an issue that was discovered and immediately fixed, the contributor should assign the bug to himself.

+

#* Plan items and other composite enhancements can stay assigned to the inbox, but have their state changed to ASSIGNED when a commitment is made to fix them.

+

# When the contributor can commit to a fixing a bug, he changes the state to ASSIGNED and sets a target milestone.

+

+

=== How bugs are FIXED and VERIFIED ===

+

# When a committer or contributor has completed fixing the bug, he should post a patch with the fix to the bug.

+

# A committer commits the changes to CVS. A contributor can request a committer to apply the patch.

+

# The committer changes the bug status to FIXED and request for the component owner or another committer to review the fix.

+

# The reviewer should review the changes and optionally confirm program behavior and mark the bug as VERIFIED.

+

+

=== How bugs are CLOSED ===

+

# With each milestone build, the VERIFIED bugs are logged and marked as CLOSED.

Bug Life Cycle

Once the bug report is filed, contributors and committers work on it, including updates to bug status. All users may contribute to the discussion by adding comments (but typically not change the status fields). The Eclipse Process Guidelines contain some good information and a handy diagram for understanding the lifecycle of an issue in Bugzilla.

How bugs are ASSIGNED

All bug should be created with the "Assigned To" field set to dd.general-inbox@eclipse.org. This allows everyone watching the list to observe bug activity.

Component owner, which is normally the leader of the sub-project owns the component, confirms that the bug is valid and assigns it to a committer or contributor.

Alternatively, if a contributor created the bug for an issue that was discovered and immediately fixed, the contributor should assign the bug to himself.

Plan items and other composite enhancements can stay assigned to the inbox, but have their state changed to ASSIGNED when a commitment is made to fix them.

When the contributor can commit to a fixing a bug, he changes the state to ASSIGNED and sets a target milestone.

How bugs are FIXED and VERIFIED

When a committer or contributor has completed fixing the bug, he should post a patch with the fix to the bug.

A committer commits the changes to CVS. A contributor can request a committer to apply the patch.

The committer changes the bug status to FIXED and request for the component owner or another committer to review the fix.

The reviewer should review the changes and optionally confirm program behavior and mark the bug as VERIFIED.

How bugs are CLOSED

With each milestone build, the VERIFIED bugs are logged and marked as CLOSED.