Christian Heimes <li...@cheimes.de> wrote: > IMHO it makes sense to define a workflow how we are going to handle > Coverity issues. Each coverity issue has an identifier and can have > information like an external reference and an action. I've seen that you > have started to create bugs in our tracker. How about we mention the > Coverity # in the bug and add a link to the bug in the "Ext. Reference" > field of the Coverity issue and set the Action to "Claimed, being worked > on".
That sounds good in principle. I'm only worried that for casual readers of either the commit messages or the tracker issues the importance of the Coverity tool might be overstated. After all, 99.99% of issues are either found by developers themselves or by gcc, Visual Studio, Valgrind, etc. It just occurred to me that for example we don't credit other tools in commit messages. That said, for users of the Coverity web interface it's clearly useful. Stefan Krah _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
