[mythtv] status of MythTV wrt Coverity Scan

Gary Buhrmaster gary.buhrmaster at gmail.com
Mon May 7 16:34:23 UTC 2012


On Mon, May 7, 2012 at 4:14 PM, Eric Sharkey <eric at lisaneric.org> wrote:
....
> I still don't understand this logic.

The logic that matters is that master is undergoing
fixes and new codes.  It is "the lastest and greatest".
Existing bugs found (if serious) would be back-ported
to compatible versions (sometimes it is not worth the
trouble for, say, something like 0.21), but more
importantly, you want the codes you are developing
to be the best they can be(*).  Static and dynamic
analysis helps that, and while the developers are
good, they have, from time to time, introduced new
bugs in the new codes they are working on and
you would prefer to find those bugs in the codes
before "shipping".  Every analysis tool finds a
different set of bugs (cppcheck and scan-build,
for example, have both resulted in fixes in different
sections of the codes).  The more the merrier.  And
you want to (first) target your upcoming release(s).

Gary

(*) For example, jya just (essentially) rewrote the
entire ROAP codes.  What matters is less what was,
than what will be.


More information about the mythtv-dev mailing list