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 "EclipseLink/Development/Bugs/Guidelines"
(→Priority) |
|||
| Line 1: | Line 1: | ||
=== EclipseLink Bug Status Guidelines === | === EclipseLink Bug Status Guidelines === | ||
| + | |||
| + | == Severity == | ||
| + | |||
| + | The Severity field is used as an indication of the filer's impression of the severity of the bug. Except in cases of abuse of this field, it should usually be left as initially set. The exception to this rule is that some bugs are clearly enhancements rather than bugs. They can be changed to Enhancements. | ||
| + | |||
| + | Enhancements are reviewed when they are initially entered, but if not targetted at that time, will only be reviewed when release planning occurs. At that time, any candidates for the upcoming release should be targetted. | ||
== Priority == | == Priority == | ||
| Line 12: | Line 18: | ||
* P4 - Nice to have, time permitting | * P4 - Nice to have, time permitting | ||
* P5 - Lower priority | * P5 - Lower priority | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Keywords == | == Keywords == | ||
Revision as of 15:47, 15 October 2008
Contents
EclipseLink Bug Status Guidelines
Severity
The Severity field is used as an indication of the filer's impression of the severity of the bug. Except in cases of abuse of this field, it should usually be left as initially set. The exception to this rule is that some bugs are clearly enhancements rather than bugs. They can be changed to Enhancements.
Enhancements are reviewed when they are initially entered, but if not targetted at that time, will only be reviewed when release planning occurs. At that time, any candidates for the upcoming release should be targetted.
Priority
Priority is an indication of the priority of the bug amoung the committer group.
The following values are used in the priority field
- P1 - Urgent bug fix. Someone should work on this immediately
- P2 - Required for Release. This fix is a requirement for the release listed in the target field.
- P3 - This is the default. Targetted for the listed release, but not considered a blocker
- P4 - Nice to have, time permitting
- P5 - Lower priority
Keywords
We use the following keywords at this time:
- test - for bugs that are issues with a test (rather than the code the test is exercising)
- performance - for bugs that describe an issue that the key effect is on performance
- contributed - should be added to a bug on any community submitted patch when it is checked in
Status Whiteboard
The following status whiteboard strings are recognized
- simple_fix - for issues where the fix is a trivial change, something that can be undertaken in a matter of minutes. Some examples of this kind of bug is a typo in an error message or a comment, a wording issue with an Error message, or an unused import in a single file.
- submitted_patch - indicates that a member of the community has submitted a patch. This allows us to search for these issues and expedite their inclusion in the product.
Summary
An issue with the build should be prepended with the string: [Build]