SageTV Community  

Go Back   SageTV Community > SageTV BETA Release Products > SageTV Beta Test Software
Reload this Page Current Bug Reports listing?
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

SageTV Beta Test Software Discussion related to BETA Releases of the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. regarding SageTV Beta Releases should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 10-10-2006, 05:22 PM
CanadianEh CanadianEh is offline
Sage Aficionado
  
Join Date: Apr 2004
Location: Colchester, VT
Posts: 434
Current Bug Reports listing?
Good evening -

I was just wondering if there was a place that currently lists all reported bugs that exist in the latest version of SageTV, specifically the latest beta. I think it would be nice to have one specific list that one could check to see if they're issue is already known and potentially fixed before needing to submit a bug report. Perhaps each incident could have a status of something like:
- Known bug
- Need additional information from other users experiencing problem
- Fixed in V 6.12

Any thoughts, guys?
__________________
My systems:
Server: AMD Phenom Quad-Core 2.3Ghz, 4GB RAM, ECS A780GM-A MB, 2x HD-PVRs (connected to DirecTV HD STBs using ethernet channel changing), 1x AverMedia A180, OS RAID-1 mirror - 2x250GB 7200rpm SATA, Media RAID-1 mirror - 2x1TB 7200rpm SATA, USB-UIRT (remote control)
Main Client: Sage STX-HD100 Media extender
Second Client: Athlon XP 4000+, 2GB MB PC3200 DDR, Asus A8N5X MB, 512MB PCI-E ATI HD Radeon 3650, 160 GB SATA - hardware mirrored
Reply With Quote
  #2  
Old 10-10-2006, 05:25 PM
Mark SS Mark SS is offline
Sage Expert
  
Join Date: Dec 2005
Location: London, UK
Posts: 608
Some sort of bug tracker would be a brilliant idea. Saves time for users and the devs!
Reply With Quote
  #3  
Old 10-10-2006, 06:18 PM
CanadianEh CanadianEh is offline
Sage Aficionado
  
Join Date: Apr 2004
Location: Colchester, VT
Posts: 434
... unless it already exists and I just don't know about it!
__________________
My systems:
Server: AMD Phenom Quad-Core 2.3Ghz, 4GB RAM, ECS A780GM-A MB, 2x HD-PVRs (connected to DirecTV HD STBs using ethernet channel changing), 1x AverMedia A180, OS RAID-1 mirror - 2x250GB 7200rpm SATA, Media RAID-1 mirror - 2x1TB 7200rpm SATA, USB-UIRT (remote control)
Main Client: Sage STX-HD100 Media extender
Second Client: Athlon XP 4000+, 2GB MB PC3200 DDR, Asus A8N5X MB, 512MB PCI-E ATI HD Radeon 3650, 160 GB SATA - hardware mirrored
Reply With Quote
  #4  
Old 10-11-2006, 07:12 AM
nielm's Avatar
nielm nielm is offline
SageTVaholic
  
Join Date: Oct 2003
Location: Belgium
Posts: 4,496
It has always been Sage's policy to deal with bugs privately -- even for betas.

The disadvantage of a public bug tracking system is that Sage does not see the difference between a bug that affects one person and a bug that affects several, but only one has reported it (and the rest see that it has already been reported).

(yes I know that if a bug system is used properly, this will not occur, but how many times in the forums do you see people complainign about a 'known' bug that actually noone ever reported?!)
__________________
Check out my enhancements for Sage in the Sage Customisations and Sageplugins Wiki
Reply With Quote
  #5  
Old 10-11-2006, 12:01 PM
GKusnick's Avatar
GKusnick GKusnick is offline
SageTVaholic
  
Join Date: Dec 2005
Posts: 5,083
Quote:
Originally Posted by nielm
how many times in the forums do you see people complainign about a 'known' bug that actually noone ever reported?!
Not to mention people who say "I have the EXACT SAME problem" and then go on to describe something completely different. Similar symptoms don't necessarily have the same underlying cause. It's probably best to collect as many bug reports as possible and let the professionals decide whether two reports actually describe the same bug.
__________________
-- Greg
Reply With Quote
  #6  
Old 10-11-2006, 12:47 PM
Goodspike's Avatar
Goodspike Goodspike is offline
Sage Expert
  
Join Date: Jul 2005
Posts: 599
Quote:
Originally Posted by GKusnick
Not to mention people who say "I have the EXACT SAME problem" and then go on to describe something completely different. Similar symptoms don't necessarily have the same underlying cause. It's probably best to collect as many bug reports as possible and let the professionals decide whether two reports actually describe the same bug.
Not to mention that the multiple reports could allow Sage to track it down to certain types of hardware or codecs.
Reply With Quote
Reply

« Previous Thread | Next Thread »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -6. The time now is 04:20 PM.

Contact Us - SageTV, LLC - Archive - Privacy Statement - Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.