Greetings from Australia I am revisiting the forums after 18mths off doing other things and like the changes and am wondering if the Parallels team would post a sticky setting out in a page or two the testing process that a build goes through. I have done a forum search but don't seem to be able to find such a posting. As a software tester for an international software company i have an awareness of how complex software testing can be. This would I believe help many users understand how complex a testing cycle is with a software build before it "goes out to users". To expect a release to be totally bug free is simplistic and unrealistic, no software company in the world would be silly enough to guarantee a totally bug free product. Testing environments can never replicate the real world day to day use of a product as much as they try to where there are thousands of users each doing different things across the world. I have noticed in some of the forums people are attacking parallels for asking users to provide testing feedback. As a software tester for a large company whilst we test for months before release we rely on our users to provide feedback on bugs that occur. Its simply impossible to replicate every scenario. I suspect I may be attacked for my comments however i believe a sticky from a senior parallels team member eplaining the process in a broad way that each build goes through before general release would be of interest to the parallels community and help everyone gain a better inderstanding of the complex issues involved in software testing. regards John
