boilerplate messages in bugs

Karl Goetz karl at kgoetz.id.au
Fri Sep 12 04:28:27 UTC 2008


On Thu, 2008-09-11 at 10:38 -0700, Leann Ogasawara wrote:
> On Thu, 2008-09-11 at 15:26 +0930, Karl Goetz wrote:
> > On Wed, 2008-09-10 at 09:32 -0700, Leann Ogasawara wrote:
> > > On Wed, 2008-09-10 at 17:41 +0930, Karl Goetz wrote:
> [snip]
> > What level of automation was it? a for loop, or someone manually going
> > and pasting into the bug reports?
> 
> It was completely automated through the use of python-launchpad-bugs.

I see.

> > I guess it depends on the level of automation.
> > If theres a human doing the pasting, i dont think its unreasonable to
> > think that a bug title that refers to /path/to/foo.c would be left out
> > of a call to test a binary kernel.
> > If its completely automatic, then that makes it somewhat harder.
> > I dont know how LP works for a 'hands off' level of automation (indeed,
> > i dont know if it can at all), so i cant comment on wether it can be
> > told to ignore some bugs in mails like that.
> 
> Using python-launchpad-bugs we could ignore posting to bug reports which
> had a specific tag.

Are their tags for source/binary problem?
Perhaps something to indicate a bug is source related (eg, copyright
issue) as oposed to binary (eg, crasher).
kk

> 
> Thanks,
> Leann
> 
-- 
Karl Goetz <karl at kgoetz.id.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20080912/14e64034/attachment.sig>


More information about the Ubuntu-bugsquad mailing list