[mythtv] Mythtv Bug 4989

Steve Hodge stevehodge at gmail.com
Fri Feb 6 12:08:02 UTC 2009

On Fri, Feb 6, 2009 at 11:07 PM, Jean-Yves Avenard <jyavenard at gmail.com>wrote:

> Hi
> 2009/2/6 Steve Hodge <stevehodge at gmail.com>:
> > The usual definition is that a bug is a piece of code that does not work
> as
> > intended. This code does do what it was designed to do - the Live TV
> > handling is something that wasn't implemented, not something that was
> > implemented but doesn't work as intended. So (IMHO) it's a feature
> request.
> Jeez, I wonder how you explain that view at your job if you're a
> software developer.
> It's okay sir, it's not a bug ; if it failed to work it's because it
> wasn't implemented... You see ; a bug is .....

As it happens I am a software developer and that's exactly how we explain it
to clients (who would otherwise file every feature request they can think of
as bugs). People developing software commercially are generally following a
specification. If the behaviour of the implementation is outside what the
spec requires then it's a bug, if you want something that wasn't in the spec
it's a feature request.

In this case the specification is stored inside the devs' heads so you'll
just have to take their word for it that the Live TV behaviour you want is
outside what they intended to do. But really, whether you want to call it a
bug or a feature is irrelevant. If the devs don't want it in trac that's
their perogative, regardless of what terminology you want to apply to the

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20090207/ae77bacc/attachment.htm>

More information about the mythtv-dev mailing list