[mythtv] Bug Report Module
skd5aner at gmail.com
Wed Feb 23 20:45:56 UTC 2005
I like the idea, but I think it'd have to be a completely seperate
entity from what developers refer to as "bugs". I know just because
something might not work, or the end user might break something,
doesn't mean it's a bug. Also, you gotta realize the quality of
end-user reports are probably going to lack good information for the
myth developer community to do much about, and there is actually ZERO
support requirements for the end users, so that means these end users
would get ZERO feedback for their submitted issues.
Like I said, it's a great idea but I think you'd have to come up with
a good model of how it'll work effectively before developing it.
On Wed, 23 Feb 2005 12:30:50 -0800, Geoffrey Kruse <gkruse at gmail.com> wrote:
> Along the lines of testing and getting myth as bug free as possible, I
> would like to propose a bug reporting module so that users can report
> bugs using the frontend interface. Typically, it is my significant
> other (not myself) who finds bugs when she is using myth, but she is
> not likely to join the dev list to report them, rather just complain to
> me that the tv is "not working". A report bugs module, similar to the
> report bugs button in Safari would make it easier for the every day
> users to get their voices/problems heard. I think this is very
> important to the survival of myth because ultimately, the majority of
> people out there are novice users.
> Any Takers?
> Geoff Kruse
> > On Feb 23, 2005, at 12:17 PM, Isaac Richards wrote:
> >> On Wednesday 23 February 2005 04:36 am, Cecil Watson wrote:
> >>> I've always had the policy of not releasing KnoppMyth w/ CVS
> >>> versions of MythTV. This was born of my own personal experience w/
> >>> CVS
> >>> versions of various apps. From reading various threads in the past,
> >>> Isaac has stated that he didn't like the idea of packaged CVS
> >>> versions
> >>> of MythTV. I don't follow the dev list closely, but I see he has
> >>> changed his mind. Apparently the idea of release candidates don't
> >>> sit
> >>> too well.
> >> I simply don't have time to do release candidates, and I really don't
> >> think
> >> most people would use them, anyway.
> >>> I don't think model of "just run CVS" is very helpful as folks
> >>> have
> >>> been bitten by the CVS bug (not saying MythTV, but various apps).
> >>> Once
> >>> bitten, twice shy. If the general attitude is "by developers for
> >>> developers", then I think this should be stated as such. I can
> >>> respect
> >>> that. I can fully understand a developer working on MythTV so he/she
> >>> can add a feature the he/she like.
> >> Well, how else is someone supposed to get a bugfix between releases,
> >> other
> >> than using CVS? I simply can't put out a new release for each and
> >> every bug
> >> that's fixed.
> >>> I love MythTV. Simply put MythTV is the way I've been watching
> >>> TV
> >>> for about 2 years now. KnoppMyth became a way for other to enjoy
> >>> MythTV
> >>> without the hassle. As a user, what can I do to help the stability
> >>> of
> >>> "released" versions? As someone that would like to make it easier
> >>> for
> >>> other to enjoy MythTV, what can I do to help the stability of
> >>> "released"
> >>> versions?
> >> Test CVS, get other people to test CVS, especially when I've
> >> announced a
> >> release is close. Report bugs. =)
> >> Isaac
> >> _______________________________________________
> >> mythtv-dev mailing list
> >> mythtv-dev at mythtv.org
> >> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
More information about the mythtv-dev