View Single Post
Old 12-30-2009, 11:30 AM   #5
Valloric
Created Sigil, FlightCrew
Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.
 
Valloric's Avatar
 
Posts: 1,978
Karma: 350515
Join Date: Feb 2008
Device: Sony Reader PRS 505
Quote:
Originally Posted by ghostyjack View Post
Thanks for this.

I don't have a problem reporting issues in the Issues tab on your Google Code page (I have raised several already, forgot one, but the rest got raised) but I usually prefer to check that it is a fault before raising it as an issue.

I don't see the point in putting unnessary work in the direction of the developer, especially one that is busy. I'm a test engineer and it normally frustrates my developers when I start submitting lots of defect reports when it turns out that there is nothing wrong, just that the software works slightly different from how I was interpreting it.
In general I prefer to have issues created on the tracker. I don't find it a chore to just add a comment and mark the issue as invalid if it really is that. I don't blame people when they create an issue for something that turns out not to be a bug, but just them misunderstanding something.*

Ignorance is not a sin. If you don't understand something, it's because someone failed to explain it to you properly. So if your developers get annoyed when you create an issue for something that has merely changed behavior, ask them why they haven't informed you about it beforehand. And if you're a test engineer with intimate knowledge of the product and something actually works differently than you think, something's probably wrong with the application design. Or again, someone failed to teach you how it really works.

It's of course a different matter entirely if there's documentation about it and you failed to read it.

Back to Sigil...

I like issue reports more than threads on the tracker since issue reports usually require my immediate attention and therefore all changes to the tracker are sent as instant email alerts.

The forum should be for discussions.

*But I do get annoyed when someone creates an issue that has already been reported, or worse still, reports one with basically zero information useful to track the issue down. The people who don't read the ReportingIssues wiki page even though it's linked right there in the issue report template and about 10 other places as well.

Ignorance is not a sin, laziness is.

Last edited by Valloric; 12-30-2009 at 11:34 AM.
Valloric is offline   Reply With Quote