Re: MediaPortal SVN-Snapshot:-01-08-2010 02-15h - Revision:24669.rar
Hi,
The situation isn't perfect. However, many of the 'bugs' reported are almost certainly due to conflicts between codecs, corrupt files on users systems and similar. Opening up mantis would result in it being filled with incorrect bug reports that will be impossible to keep track of and fix. The same bug will be reported five times with different wording, and when a moderator deletes it, it will reappear within hours!
Mantis needs to be kept for the bugs that can be confirmed by the team. Inevitably some bugs will be missed, but I think the current, extremely stable, state of MediaPortal is a testament to this approach working.
However, please keep reporting the bugs, keep nagging if they seem to be missed, and above all, please respond to requests for further testing/logs that will actually allow the developers to work out what is going wrong.
Best wishes,
Mark
Have you considered opening up mantis (or starting a new JIRA or Bugzilla) to control all these user reports? To me all these SVN threads is a giant mess and it seems a large part of the reports gets lost in the mix and forgotten. I think people generally get frustrated with report bugs with full logs, only to have them lie forgotten in an old SVN thread. There must be something better than this.
Hi,
The situation isn't perfect. However, many of the 'bugs' reported are almost certainly due to conflicts between codecs, corrupt files on users systems and similar. Opening up mantis would result in it being filled with incorrect bug reports that will be impossible to keep track of and fix. The same bug will be reported five times with different wording, and when a moderator deletes it, it will reappear within hours!
Mantis needs to be kept for the bugs that can be confirmed by the team. Inevitably some bugs will be missed, but I think the current, extremely stable, state of MediaPortal is a testament to this approach working.
However, please keep reporting the bugs, keep nagging if they seem to be missed, and above all, please respond to requests for further testing/logs that will actually allow the developers to work out what is going wrong.
Best wishes,
Mark
United Kingdom