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 and Target Version) |
|||
| Line 9: | Line 9: | ||
== Priority and Target Version == | == Priority and Target Version == | ||
| − | + | Bugs will be triaged approximately a weekly basis to set Priority and target version. | |
| − | + | ||
| − | + | ||
Target Version can be either set to a specific version or not. The following Target versions indicate that a specific version has not been chosen: | Target Version can be either set to a specific version or not. The following Target versions indicate that a specific version has not been chosen: | ||
| Line 19: | Line 17: | ||
* no value - this means the bug has not been triaged and the priority and target version have not been set by the team | * no value - this means the bug has not been triaged and the priority and target version have not been set by the team | ||
| − | If the "Target Version" set "Future" the priority field indicates the bug's priority relative to other bugs with a "Future target". i.e. P1 bugs will be targetted before P2 bugs, P2 bugs before P3 bugs and so on... | + | If the "Target Version" is set to "Future" the priority field indicates the bug's priority relative to other bugs with a "Future target". i.e. P1 bugs will be targetted before P2 bugs, P2 bugs before P3 bugs and so on... |
If the Target version is set to a specific version, the following values are used in the priority field | If the Target version is set to a specific version, the following values are used in the priority field | ||
| Line 27: | Line 25: | ||
* P3 - This is the default. Targetted for the listed release, but not considered a blocker | * P3 - This is the default. Targetted for the listed release, but not considered a blocker | ||
* P4 - Nice to have, time permitting | * P4 - Nice to have, time permitting | ||
| − | * P5 - Lower priority | + | * P5 - Lower priority - likely to be deferred |
== Keywords == | == Keywords == | ||
Revision as of 10:53, 15 April 2009
Contents
EclipseLink Bug Report 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 and Target Version
Bugs will be triaged approximately a weekly basis to set Priority and target version.
Target Version can be either set to a specific version or not. The following Target versions indicate that a specific version has not been chosen:
- "Future" - The goal is to make this the only setting for triaged bugs
- "1.1x" - deprecated, 1.1x bugs will be retriaged and have a new target and priority set
- no value - this means the bug has not been triaged and the priority and target version have not been set by the team
If the "Target Version" is set to "Future" the priority field indicates the bug's priority relative to other bugs with a "Future target". i.e. P1 bugs will be targetted before P2 bugs, P2 bugs before P3 bugs and so on...
If the Target version is set to a specific version, 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 - likely to be deferred
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
The summary field of an issue with the build should be prepended with the string: [Build]