EMF Facet/Bug Process

Bug process

The user reports a "bug"

• Report a bug (where bug is a bugzilla item)
  • specify the version in which the bug appears

The project leader:

• Mark the bug with one of the following priority:
  • P1: Urgent
  • P2: Has to be fixed before the next minor release
  • P4: Should be fixed before the next minor release
  • P5: No fix planned for the next minor release

P3 is the default priority value : reserved to indicate that the bug has not be prioritized.

The committer checks the bug report

• If the version number is empty:
  • Ask the version to the user
• Try to reproduce the bug
  • If the contributer cannot reproduce the bug
    • the bug mark the bug as "worksforme"
  • If the contributer can reproduce the bug
    • Adjust the version number to the oldest maintained branch on which the bug appears

The contributer proposes a patch

• Create a git commit
  • containing:
    • the bug fix
    • the documentation update (including the "New and Noteworthly")
    • unit tests
  • and having a well-formed comment:
    • the first line contains the bug label : Bug <bug-id> - <bug-label>
    • lines containing the explanations of the commit
    • an empty line
    • the "signed-off-by" line to confirm that him contribution complies with http://www.eclipse.org/legal/CoO.php

Bug %bug-id% - %bug-label%

Signed-off-by: %firstName% %lastName% <%e-mail%>

• push this commit to Gerrit

The committer reviews the patch

• Assign the bug to himself
• Do the code review and vote via Gerrit
  • Check that the copyright header is well-formed
  • The contributor sections have been updated
  • The commit message contains the "Signed-off-by"
• Submit the path via Gerrit
• Add a comment to the bug attachment indicating the commit id.
• Mark the bug as "RESOLVED" "FIXED"
• Set the "Target Milestone" field

The user checks the fix

• Get the next milestone build (or integration build).
• Check that the bug is fixed.
  • If the bug is fixed
    • Close the bug.
  • If the bug is not fixed
    • Reopen the bug.

The project leader cleans the bugzilla entries

• Before the release (in May)
  • Close the bugs which have not be closed by the user.