Quality Control Center
Have you encountered some unexpected behaviour in Revolution? You think it might be a bug? We want to hear from you. User reports are vitally important to us and we read every one. We have a Quality Center devoted entirely to managing bug reports. However, before you make that report STOP! Please, help us to help you and read through this checklist first.
1) Are you sure it’s a bug? Before you report it as such, check your code for errors and gotchas. If you can, get someone else to check it. A great way to do this is to take it to the Revolution forums, and see if anyone else has seen the same behaviour. Maybe that unexpected behaviour is just something you haven't understood about Revolution. Maybe it’s a typo in your code - very very easy to do and equally easy to miss when you are checking your own code.
2) Ok, so you're fairly sure it’s a bug. Next, do a search in the Quality Center and see if its already been reported. This isn't always the easiest thing to do, as different people will report things in different ways, but it helps to do a quick check on some keywords and reduces the number of duplicate reports our engineers have to identify and deal with. If you do find a similar bug report, you may want to add comments to it, as the more examples of a bug our engineers have to work with, the easier it can be to identify and fix the cause of the problem.
3) It's a bug, and you can't find a similar report. Great. Please file that report, considering carefully what category and priority to give it, and making sure you tell us as much as you can about the circumstances, your platform and OS, the version of Revolution you were using and how to reproduce the problem. If you miss out any of this information, our engineers will have to write to you and ask, and this will delay processing of the report.