Zen

Source string Source string

479/10000 · 479

The string is read only.

English Actions
The image below presents a general flow chart for bugs in the typical case. The flow is bi-directional: a bug can revert to a previous status if, for example, a proposed fix is incomplete.
program_management::fedora-bug-lifecycle.png
The table below summarizes the statuses. More details, including additional keywords, flags, and resolutions are given in the following sections.
Resolutions
The table below describes the resolutions that can apply to the _CLOSED_ status.
Priority and Severity
Severity
The _Severity_ field is used to indicate the bug's importance. The values for the severity field should be assigned with reference to the following guidance:
_Urgent_: the bug makes whole system unusable (or it is a security bug, which is per definition urgent)
_High_: the bug makes the program in question unusable, or a major packaging guideline violation (license problem, bundled library, etc)
_Medium_: a real bug which makes program more difficult to use, at least part of the program is available; possibly workarounds are available
_Low_: anything else - cosmetic issues, corner cases with unusual (non-default) configurations, etc.
The _Urgent_ setting should not usually be used for hardware-specific bugs: a bug which causes the entire distribution to be affected but is restricted to a single specific type of hardware should usually be set to _High_. For instance, if a bug prevents X.org working correctly on a single particular graphics chipset, use the _High_ severity, not _Urgent_.
For most packages, most issues are likely to be of _Medium_ severity. These are not hard and fast rules. Use your best judgement in setting the severity field appropriately. There are obvious cases which require the exercise of judgement—for instance, a bug which affects more than just the program in which it occurs, but less than the 'whole system'.
Priority
The _Priority_ field may be used, at their choice, by maintainers to keep track of the order in which they wish to address bugs in their package(s). This may be done with relation to the severity setting, or by any other method the maintainer chooses, at the maintainer's sole discretion. It may also be entirely ignored, if the maintainer in question does not wish to use it No-one other than the maintainer or team responsible for a particular bug should change this setting.

Loading…

User avatar None

String updated in the repository
The _Priority_ field may be used, at their choice, by maintainers to keep track of the order in which they wish to address bugs in their package(s). This may be done with relation to the severity setting, or by any other method the maintainer chooses, at the maintainer's sole discretion. It may also be entirely ignored, if the maintainer in question does not wish to use it No-one other than the maintainer or team responsible for a particular bug should change this setting.
The _Priority_ field may be used, at their choice, by maintainers to keep track of the order in which they wish to address bugs in their package(s). This may be done with relation to the severity setting, or by any other method the maintainer chooses, at the maintainer's sole discretion. It may also be entirely ignored, if the maintainer in question does not wish to use it No-one other than the maintainer or team responsible for a particular bug should change this setting.
a year ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

16732946 String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?", read-only
Source string location
./pages/bug_status.adoc:50
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/bug_status.pot, string 19