Skip to main content
Jump to: navigation, search

Difference between revisions of "EMF Facet/Bug Process"

(Bug process)
(Bug process)
Line 14: Line 14:
 
P3 is the default priority value : reserved to indicate that the bug has not be prioritized.  
 
P3 is the default priority value : reserved to indicate that the bug has not be prioritized.  
  
The contributer :
+
The contributer:
 
* If the version number is empty:
 
* If the version number is empty:
 
** Ask the version to the user
 
** Ask the version to the user
 +
 +
The committer:
 
* Try reproduce the bug
 
* Try reproduce the bug
 
** If the contributer cannot reproduce the bug
 
** If the contributer cannot reproduce the bug
Line 22: Line 24:
 
** If the contributer can reproduce the bug
 
** If the contributer can reproduce the bug
 
*** Adjust the version number to the oldest maintained branch on which the bug appears
 
*** Adjust the version number to the oldest maintained branch on which the bug appears
 +
 +
The contributer:
 
*** Create a patch containing:
 
*** Create a patch containing:
 
**** the bug fix
 
**** the bug fix
Line 29: Line 33:
 
**** confirm, in the attachment comment, that him contribution complies with http://www.eclipse.org/legal/CoO.php
 
**** confirm, in the attachment comment, that him contribution complies with http://www.eclipse.org/legal/CoO.php
  
The committer :
+
The committer:
 
* Assign the bug to himself
 
* Assign the bug to himself
 
* Commit the patch
 
* Commit the patch

Revision as of 09:18, 13 May 2015

Bug process

The user:

  • create a bug
    • 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 fixed before the next minor release
    • P4: Should be fixed before the next minor release
    • P5: No fixed planned for the next minor release

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

The contributer:

  • If the version number is empty:
    • Ask the version to the user

The committer:

  • Try 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:

      • Create a patch containing:
        • the bug fix
        • the documentation update (including the "New and Noteworthly")
        • unit tests
      • attach the patch the bug

The committer:

  • Assign the bug to himself
  • Commit the patch
  • Add a comment the bug attachment indicating the commit id.
  • Mark the committed attachments "iplog+"
  • Mark the not committed attachment "iplog-"
  • Mark the bug as "RESOLVED" "FIXED"
  • Set the "Target Milestone" field

The user:

  • 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:

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

Back to the top