CCP Orion wrote:Andreus Ixiris wrote:Nicholai Thomasovich wrote:People posted in the test forum that it was happening to them..
I'm beginning to see just how little the opinions of testers mean to them.
The opinions of players investing their own time in helping us improve the game means the world to us. The issue here is that for specific client side bugs, in this case the window location code, erroneous behaviour can be tough to verify/reproduce. This is because you guys have us outnumbered and are running on more diverse hardware. As CCP Gangleri detailed earlier in this thread the window placement bug, was reproducible in house but in a more benign form, thus we decided to go ahead with the patch.
A fix for this issue is coming next tuesday, and a refactoring of the window position code is coming in the winter release.
it would be nice if you also commented on my somewhat longer
previous post.i actually believe that you drastically need to change the way you handle bugs: IF there is a KNOWN bug, FIX the bug FIRST, dont roll out the update or new functionality. as you had to admit and as we all see now, you cannot forsee how many people will be affected by a bug. people can wait a week longer for sure for new things to come, but they get mad (for good reason) when they see new bugs introduced (that are not necessary imoh).
if window layout (concisely remembering previous state) is so hard and difficult to do you might earn some understanding if you explained some details how it is done and what actually caused the problem. i believe the community will put a finger into this bug and will want to know what has been the root cause for this. lets see if this isnt in the end just some lazy programming and if you had the courage to admit it.
your CEO has stated "put quality first"** - this means dont roll out bugs to production environment, dont make a risk assessment on the bug, just fix it first. imagine some business / banking software had a hard to find bug, and every 1 wire transfer out of 1 million was performed erroneous, it is just unacceptable - even more rolling it out if you KNEW there was a "dormant" bug.
THIS MENTALITY OF YOURS HOW TO HANDLE BUGS HAS TO BE ESCALATED TO TOP MANAGEMENT. this kind of ignorance and arrogance is becoming unbearable.
let me give another constructive suggestion to your problem of doing QA. for sure it is hard to find a bug on sisi when only a few players are using it (compared to tranquility, and what are you suppsed to do alone in a static sandbox). how about you do the following:
- announce the availability of a patch, ready to be tested on a new "quality first" test system
-
freeze this patch level on the new test server
- give people 2 million free skillpoints (on test server) as incentive to go there and test something out
- even more, maybe give people about 24k free permanent SP on
tranquility as another incentive to do QA for you. or increase skilling rate on
tranquality to e.g. factor 1.5 for the time you spend on new test server to find bugs.
- keep the test system runnning until the patch has been proved ok and rolled out into production, then take it down
**actually i dont find the source right now, please correct me if i had a wrong impression here about the CEO's views. please notice how much the community values
Commit to excellence (CSM) - competing with new functionality and other features! (
July 2011 Prioritization Crowdsourcing).