Here's what I envision:  A new rhythmbox is released and pushed out to
the masses.  It incorporates a new feature called crazy jukebox where it
makes all your windows wobble to the music (please don't code this!).
The developer is so excited about this new capability that it is pushed
out the door and enabled by default.

Joe User sees a new rhythmbox and selects update.  He wants to listen to
music--BAM rhythmbox crashes (presumably because either wobbly windows
is not enabled or compiz is not running).  Crash dialog comes up
presenting 3 options:  Quick Bug Report, Detailed Bug Report, Quit.

The Quick Bug server gets hammered with reports of rhythmbox crashes.
Server is set to send email notice to developer after 5 hits in the past
hour--automatic triage.  Quick Bug reporter has no expectation of
getting email notices of bug fix progress.  Developer digs the crud out
of his eyes the next morning and sees some detailed bug reports from
irate users and a warning email from the Quick Bug server.  Something is
up with the new version.  A quick read of the bug reports:  Work around:
Turn Off Crazy Jukebox!

Developer quickly sees that this new rhythmbox capability interferes
with several use cases:  older machines without compiz, headless
machines, machines with compiz but with wobbly turned off, etc . . .
Developer makes changes  adds a glx check, turns off crazy jukebox by
default and adds a warning dialog when it is activated.   New release is
submitted to Q/A.

Q/A is busy and new rhythmbox is at the bottom of the stack.  Quick Bug
server sends an email to Q/A when reports exceed 20 during the past
hour.  Whoa, better look at rhythmbox.  Patches submitted, need to
perform test suite on rhythmbox (or whatever Q/A does) then push the
release.  Q/A runs a Quick Bug report on rhythmbox to see that the
growing mountain of bug reports is dropping quickly.

Back to work on Bug #1.

-- 
Automatic bug reporting not so automatic
https://bugs.launchpad.net/bugs/196172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to