Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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) |
(→Bug process) |
||
| Line 24: | Line 24: | ||
The contributer: | The contributer: | ||
| − | + | * Create a patch containing: | |
| − | + | ** the bug fix | |
| − | + | ** the documentation update (including the "New and Noteworthly") | |
| − | + | ** unit tests | |
| − | + | * attach the patch the bug | |
| − | + | ** confirm, in the attachment comment, that him contribution complies with http://www.eclipse.org/legal/CoO.php | |
The committer: | The committer: | ||
Revision as of 09:22, 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 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 patch containing:
- the bug fix
- the documentation update (including the "New and Noteworthly")
- unit tests
- attach the patch the bug
- confirm, in the attachment comment, that him contribution complies with http://www.eclipse.org/legal/CoO.php
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.
- If the bug is fixed
The project leader:
- Before the release (in May)
- Close the bugs which have not be closed by the user.