[Buildbot-devel] Volunteering and some suggestions.

[Marcus Lindblom]

On 2009-12-23 20:34, Dustin J. Mitchell wrote:
> (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:
>>
>> [notification]
>> 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".

Perhaps we could steal^h^h^h^hadopt some procedure from twisted, that 
has a bunch of extra fields for patches such as 'has patch', 'patch 
needs improv', 'need test', 'need doc'. Etc.

Then ppl could triage better, and we could more easily see which patches 
are applicable or not.

Perhaps it's too much overhead, but something in that direction might help?

Cheers.
/Marcus