[Buildbot-devel] Volunteering and some suggestions.
Dustin J. Mitchell
dustin at zmanda.com
Wed Dec 23 19:34:02 UTC 2009
(I see this message was much-delayed, but it's a good excuse to bump
this thread up)
On Mon, Dec 7, 2009 at 1:26 PM, Tim Hatch <tim at timhatch.com> wrote:
> If your goal is that ticket updates get cc'd to the list, that's pretty
> easy. In trac.ini:
> smtp_always_cc = buildbot-devel at lists.sourceforge.net
This is done - messages are going to buildbot-commits at lists.sourceforge.net
> Depends on how you define "issues that contain a patch." If you want a
> custom report that lists tickets with attachments, or have [PATCH] in
> the summary, that wouldn't be too hard. Emailing periodically isn't a
> builtin feature, but could be done with cron.
I think that this is more a matter of having folks grooming Trac
regularly - there are lots of tickets with patches that aren't
attachments, and other tickets with attachments that don't work and
have comments to the effect of "hmm, try again".
I'm going to spend some time while I'm away from Amanda on getting the
list of 0.7.12 bugs shortened up, and get a release out probably on
Open Source Storage Engineer
More information about the devel