[Tracker-discuss] triage and other matters

[Kurt B. Kaiser]

> On 11/8/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>
>> Paul Dubois schrieb:
>> > Do the developers want a triage team (a list of people who receive
>> > email when a new issue is opened?). (As typically implemented this
>> > does not put them on the nosy list for the issue, just makes sure
>> > somebody sees every new issue).
>>
>> There currently is a mailing list for that:
>> python-bugs-list at python.org.  You can see the archive at
>>
>> http://mail.python.org/pipermail/python-bugs-list/
>>
>> We definitely want to keep it; it is currently configured to get
>> *all* changes to issues (not just when an report is added). Whether
>> this is also needed should be discussed (by default, it should
>> continue to work the way it always did, but if roundup offers
>> alternative features, we may want to use them).
===========================
"Paul Dubois" <pfdubois at gmail.com> writes:

> My experience, even on a smaller (much!) tracker, is that sending all
> changes to everyone on a list will wear out the people on that
> list. With roundup I think it works best to send the *new* issues to
> that list and then let the nosy mechanism do its thing. The nosy
> mechanism is *the* genius invention in Roundup, I believe.

There is the additional issue of the weekly Patch/Bug status report.
Currently, this is created by analyzing the mail from the bugs and
patches lists for opened/reopened and closed items, plus a simple scrape
of the total number of open/closed issues from a SF webpage.

I suppose there is a way to get this information from the Roundup
database, but it seems like a total rewrite of the report would be
needed to do that.

-- 
KBK