Re: [cdt-dev] automation of policy violations in bugzilla
I'm done. I'm not sure an automated script is necessary. The rules in the end are pretty simple. It's just a matter of getting in the habit. Here's what they are:
1) If you apply a patch or derive from it, mark the patch attachment as iplog+. You need to do an analysis on it anyway to decide whether to IPzilla it so that should be a trigger to set the flag.
2) Assign the bug to yourself. Again, inboxes can't commit code ;). I am using the assignee to figure out who applied the patch. If a bug has multiple patches applied by different people, then the last one who applied one should be good enough.
3) Set the target milestone to the next one available. We need to know what release the patch first appears in.
This is all stuff we should be doing anyway.
On Wed, Jun 3, 2009 at 4:44 PM, Elena Laskavaia <elaskavaia@xxxxxxx>
Does anybody know how to automate policy enforcement in bugzilla? (Such as iplog flag should be set on contributor patch if pr is fixed kind of)
Poor Doug setting iplog flags for a week now...
If we can have a script that runs overnight and send us report of violations it would be a lot better for next time around
(assuming we cleaned it up now it would very small number of items) and responsible
persons would fix that themselves...
cdt-dev mailing list