Re: abandoned bug reports

[Dmytro O. Redchuk]

On Sun 20 Feb 2011, 22:58 Graham Percival wrote:
> Hmm.  If you get mail with fetchmail, I recommend adding this to
> your .procmailrc.  If you're using imap, then I'm sure that gmail
> can do this kind of filtering for you already.
> 
> :0
> * ^List-ID: LilyPond Bug Reports <bug-lilypond.gnu.org>
> * @googlecode.com
> 0bug-lilypond-ignore
> 
> Filtering out all those automatic messages cuts the messages to
> bug-lilypond by half, making it much easier to spot new issues.
Yes, i have nice .procmailrc; however i read gmail with imap and google
filters mail for me, nicely. It does that in a way i configured it and i don't
consider reconfiguring it so far.

((i don't want to ignore those messages; let's assume i don't count reading
them as bugsquadder's job))

> > After "processing" all threads this way -- i look into "issues to verify".
> 
> Please no.  If there are any emails left -- ANY emails at all --
> then process them.  Dealing with emails takes COMPLETE priority
> over verifying issues.

---------8<---------------
On Mon 14 Feb 2011, 13:42 I wrote:
> On Sat 05 Feb 2011, 18:39 Graham Percival wrote:
> > How did all seven people miss those emails?
> As for me, personally --- i figured out that i had had wrong priorities.
---------8<---------------

> Of course, this goes for all the other bug squad members, too.
Oh, well, i see, ok.

> check through all the emails.  If you see an email saying "thanks,
> added as issue 1234", then stop reading and delete the whole email
> thread.
Or Shift+F, or Alt+t;d<enter> or anything else. It's not a problem to deal
with mailbox.

> >  * ... every issue report in the tracker would contain code to verify with.
> Yes, absolutely!
Would it be valid action to mark as invalid those issues which do not contain
code or description? I doubt it would. What we can do with that then?

> > Better reports are easier to deal with.
> Of course -- and one way to get better reports is to reject bad
> reports.  Don't say "oh well, maybe somebody else can handle
> this".  Reply immediately to say "I'm sorry, but I cannot
> understand this report".
Great, thanks.

Mmm.. Do you mention emails to bug-lilypond or "badly reported issues" in the
tracker? Or both?-)

Oh, yes, i see, http://code.google.com/p/lilypond/issues/detail?id=1523#c2.

Thank you .)

-- 
  Dmytro O. Redchuk
  Bug Squad