It is frustrating to find issues in a new revision, I get it, me too.. But, imagine you are a support engineer looking at the bug report system...after all its the primary input data mechanism to support/engineering feedback...  you see one of...
 
a). there is nothing there, you think "oh, great, off to the pub, no need to check the forum"
b). one bug report on some issue.. thinks "meh, its ok, I will take a look at that some time, mebbe Monday"
c). 20 or 30 bug reports of identical issues with slightly different steps, or system setups.."Oh poop!, I better get on it!"
 
with CW staff spending their own, weekend time in here to help, its a little frustrating to see that as users, we are not doing our part in helping to get these bugs resolved...
 
http://www.cakewalk.com/support/contact/problemreport.aspx
 
post it there, first!
 
minor tiff = done
 
and yes, I am un engineer..lol
 
 
 
 

Mystic38 - agreed - the most constructive thing we can do if we notice something, and it seems reproducible on our end, is to use that link, detail the issue clearly, and inform the Bakers who are quite clearly working their tail feathers off to address things that need attention.

When I'm not sure if it's a bug, I first post it here. In fact, I posted one today in which others couldn't recreate the issue. I later realized it was a stupid user error.

Mystic, im not sure why or how but I agree with everything you post in this forum.
including this, good post !
 
agreed 100%.

I'm mixed. Make sure it is not user error than submit a bug report. I try not to spam cake with my own foolishness.

If I can't figure it out or I'm confident of a bug, then I submit.

QA simply want exact steps to reproduce bugs. Clean and dry.
If there are lots of hazy similar bugs however around a similar area then they get their testing gloves on. I'm not sure whether Cake has manual or automated testing but generally it's a combination of both...Once QA are sure they have a reproducable bug off they go to the developers for a little discussion...

I try to post here, to give a shot at it being something simple I have not done correctly, and I also search the forum to see how other similar issues.
 
I would hate to take time away from a developer by submitting something as a bug prior to some other eyes looking at it first - a la the forum.  And, many times searching the forum has provided answers as to what I need to change to get something to work, etc.
 
Bob Bone
 

> a la the forum
Or QA :)