[bt-devel] handling bug reports

Thomas Abthorpe thomas at stthomasanglican.org
Mon Nov 23 10:17:43 MST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 23 Nov 2009 15:50:00 +0200
Jaak Ristioja <Ristioja at gmail.com> wrote:

> Agreed. But then we need someone who would assign the bugs to individual
> developers in case we do not do that ourselves.

I unofficially volunteer.

I have been wading in and out of the tracker, as part of our Bug-a-thons
trying to triage them, the next step, obviously is assignment. I will make a
reasonable effort assign the calls to who I think most recently touched the
code in question to address.

Part two, is something that may take a little longer. I want to parse the
assigned bugs, and then send a nag-mail to the responsible developer, and
along the same vein, parse the un-assigned and send to the developers list,
so we have a reminder of open bugs.

My $.002 (USD)

- -- 
Thomas Abthorpe

http://www.bibletime.info
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)

iEYEARECAAYFAksKw8EACgkQ5Gm/jNBp8qB7NQCfW22YKVGAfKRRzNhubCY+qXcn
mSQAn3X6hAnrfeYgy05kDZUvXv+TEswh
=B3xD
-----END PGP SIGNATURE-----


More information about the bt-devel mailing list