Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EMF Facet/Bug Process"
(→Bug process) |
|||
| Line 24: | Line 24: | ||
The contributer: | The contributer: | ||
| − | * Create a | + | * Create a git commit |
| − | ** the bug fix | + | ** containing: |
| − | ** the documentation update (including the "New and Noteworthly") | + | *** the bug fix |
| − | ** unit tests | + | *** 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> | ||
| + | *** 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 him commit to gerrit | ||
The committer: | The committer: | ||
Revision as of 08:43, 25 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 committer:
- If the version number is empty:
- Ask the version to the user
- 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
- If the contributer cannot reproduce the bug
The contributer:
- 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>
- an empty line
- the "signed-off-by" line to confirm that him contribution complies with http://www.eclipse.org/legal/CoO.php
- containing:
Bug <bug-id> - <bug-label> Signed-off-by: <firstName> <lastName> <<e-mail>>
- push him commit to gerrit
The committer:
- Assign the bug to himself
- Commit the patch
- The first line must contains the bug id and label :
Bug <bug-id> - <bug-label>
- Add a comment to 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.
- If the bug is fixed
The project leader:
- Before the release (in May)
- Close the bugs which have not be closed by the user.