[Tracker-discuss] triage and other matters

[Paul Dubois]

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.

One can combine that with a periodic 'roundup-reminder' script or two on a
cron job; this sends a list to each developer of the open issues assigned to
them, and another can send a list of unassigned issues to some set of
people. I run these twice a month, for example, with the entire development
team getting the 'unassigned' list.

This brings me to an observation: the tracker as checked in consists of the
'template' area but does not have a spot for the rest of what one needs: the
crontab, server-ctl, server configuration file, etc. I usually have those in
the parent directory of the tracker but perhaps it is too late for that.
Anyway, we need a spot for this meta-stuff.

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).
>
> Regards,
> Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061108/3171c5a0/attachment.htm