Eric Wilhelm wrote:
> # from Michael G Schwern
> # on Thursday 11 September 2008 14:17:
>
>> At first glance this new system is going to generate a lot more work
>> per report. Let's step through the old procedure...
>>
>> 1. Read report
>> 2. Reply to report
>
> Did you actually get every report on a CC? I never seemed to get more
> than a random sampling.
I don't know, I've never done an analysis. Regardless, that's orthogonal.
The new system can mail me every report itself rather than rely on individual
author settings.
> I also don't quite understand your assessment of the workflow. How many
> times per day do you need to contact the tester about the report? If
> multiple testers uncover the same bug, I just fix the bug.
If you can make that argument, I can make the argument "what, you can't just
delete some email?" about getting the odd false negative CC'd to you.
Do you automate your module releases? Why?! How often do you release
modules, a few a week, tops? Guh, if you need to release a module, I just
release the module! [1]
I still have to go through the clicky process to see what each report is,
which is more cumbersome than just reading email.
I still can't delete things from the queue.
I still don't get reports immediately.
And when I do need to reply, I still have to go through an annoying process to
answer a bug about software that I write for free. And I'm already annoyed
because there's a bug.
So you'll understand that my tolerance for UI annoyances at that point is
very, very, very low.
This is a process I'm going to be doing probably several times a week for
YEARS. Yes, I want that process streamlined.
[1] For the sarcasm impaired, that was sarcasm.
--
But there's no sense crying over every mistake.
You just keep on trying till you run out of cake.
-- Jonathan Coulton, "Still Alive"
