[opensuse-factory] Bugzilla: Changed Definitions
In the past, we at SUSE - and therefore now at Novell OPS BU - defined the severities in bugzilla in a way that is now different from nearly everybody else. We're standardizing now on the definitions given at http://en.opensuse.org/Bugs/Definitions. The severity definitions are now the same as in most other open source projects, so that we speak the same language and reduce confusion. The major changes we're doing are basically: * Severity Blocker means "Blocks development and/or testing work" * Severity Critical means "Crash, loss of data, corruption of data, severe memory leak" * We'd like to ask you to fill in the "Found by" field correctly, this will be "Beta-Customer" for openSUSE community members before a release and "Customer" if you file a bug after the release. * Novell will use internally both severity and priority for handling bug reports. We'd like you to use the changed severity definitions for every new bugreport that you are filing and also set the "Found by" field. We hope that these changes reduce some confusion and help us at Novell to better prioritize and fix bug reports, Thanks, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger schreef:
In the past, we at SUSE - and therefore now at Novell OPS BU - defined the severities in bugzilla in a way that is now different from nearly everybody else.
We're standardizing now on the definitions given at http://en.opensuse.org/Bugs/Definitions. The severity definitions are now the same as in most other open source projects, so that we speak the same language and reduce confusion.
The major changes we're doing are basically: * Severity Blocker means "Blocks development and/or testing work" * Severity Critical means "Crash, loss of data, corruption of data, severe memory leak" * We'd like to ask you to fill in the "Found by" field correctly, this will be "Beta-Customer" for openSUSE community members before a release and "Customer" if you file a bug after the release. * Novell will use internally both severity and priority for handling bug reports.
We'd like you to use the changed severity definitions for every new bugreport that you are filing and also set the "Found by" field. We hope that these changes reduce some confusion and help us at Novell to better prioritize and fix bug reports,
Thanks, Andreas
Last year i got comments on prioritize them.. Since than I report them, with p5, and minor, or normal. After scanning, the priority and severity can be set by the one that takes the bug? -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.26-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.0.42 (x86_64) Alpha0 KDE: 4.1.00 (KDE 4.0.99 (4.1 RC1+)) "release 13.1" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball <monkey9@iae.nl> writes:
Andreas Jaeger schreef:
In the past, we at SUSE - and therefore now at Novell OPS BU - defined the severities in bugzilla in a way that is now different from nearly everybody else.
We're standardizing now on the definitions given at http://en.opensuse.org/Bugs/Definitions. The severity definitions are [...] Last year i got comments on prioritize them.. Since than I report them, with p5, and minor, or normal. After scanning, the priority and severity can be set by the one that takes the bug?
Correct, the priority and severity is validated and set by the final bug owner. Please do not change it afterwards - if you disagree, comment on it. I explained this on the wiki page as well, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (2)
-
Andreas Jaeger
-
Oddball