Bugzilla: Changed Definitions

1 Star2 Stars3 Stars4 Stars5 Stars (5 votes, average: 4.6 out of 5)
Loading ... Loading ...
Tuesday, July 22nd, 2008 by Andreas Jaeger Digg!

We are 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 are 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 would 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 would 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.


13 Comments »

Comment by Livio
2008-07-22 18:32:35

You’re messing around a little bit.

Comment by Beineri
2008-07-22 19:45:13

Care to explain?

 
Comment by Andreas Jaeger
2008-07-23 07:35:49

Not sure what you mean - to me it looks more we had a mess before and clean it up now ;)

Comment by Livio
2008-07-23 07:43:11

Blocker in other bugzillas mean “blocks program from using”/etc.

That’s why I written that you’re messing around a little bit.

(Comments wont nest below this level)
Comment by Andreas Jaeger
2008-07-23 07:47:17

Livio, could you give me a URL and citations as reference, please. I check e.g. GCC (http://gcc.gnu.org/bugzilla/page.cgi?id=fields.html#bug_severity) which has “Blocks development and/or testing work”. So, this is the same as our definition.

 
 
 
 
Comment by AlbertoP
2008-07-23 02:22:04

If possible, make the “Found by” field default unique, and default to “Customer”. I don’t see any advantage in distinguishing between beta-customer and customer.

Regards,
Alberto

Comment by Beineri
2008-07-23 08:31:25

I have opened a Bugzilla request about defining a default role for oneself - let’s hope it will be implemented.

 
 
Comment by AlbertoP
2008-07-23 02:26:04

Another consideration: community members technically are not customers, because they don’t buy anything. Why not a “community user”?

Comment by Andreas Jaeger
2008-07-23 08:12:35

Good idea, I’ll discuss it. It would indeed make life easier.

 
Comment by Andreas Jaeger
2008-08-07 07:32:34

This has been implemented now - you can use “community user”. Thanks for the suggestion.

 
 
Comment by jengelh
2008-07-23 18:31:11

I always assumed “Beta-Customer” meant the group of (traditional) Beta testers (= no one after beta tests became public), i.e. those that were eligible for a SUSE box. Not that “Beta-Customer” implied that you do get the free SUSELinux box — the field is just for statistics.

 
Comment by Bolek
2008-07-30 02:13:53

What about SLES and SLED corporate users? Some of the bugs found in there are also present in OpenSuSE (never addressed). Should we go through official channels where it will be directed down stream to OpenSuSE or should we post it here as a ‘customer’? I agree with some of the comments above that the word ‘customer’ indicates someone who pays for the services. It definitely does not apply to an OpenSuSE community member as s/he does not pay for the product/support per se.

Comment by Andreas Jaeger
2008-07-30 06:08:11

Bolek, if you have a support contract with Novell, you should use the official channel to report bugs for SLES/SLED.

If you encounter a bug in SLED/SLES and find it in openSUSE as well, you can always report it against openSUSE.

 
 
Name
Email for notification (will not be published)
Website (optional)
Spam protection: Sum of four + 8 ?

Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.