General


Ryzom Forge Public Meetings agendas & reports

@Moniq and Revvy.

It's a well known fact that the testing team is missing working force.
In my original post, I wasn't directly targeting the testing phase. The point was, pushing a big changes live and then fix the issue step-by-step is not a good approach (specially when the changes is meant to change people habits) and here I am not talking about testing the product before delivery.

About waiting, well, we have been waiting 2 years (something like that, I lost the count) before seeing a change related to a certain event (and the change was actually visible during the event but vanished at the next reboot) live on Atys... so waiting couple of months before a patch is more than OK.
Yes you are right, testing is not the only problem and I personally do not understand why there is so rush with (some) changes when, by me, it is not ready to release yet. But it always ends with the testing. And we need much more testers than 2.5 or whats the average per change :/
+10
One thing that may help in the future is a combination of communication and patience. I suspect I'm not the only one that would rather hear, "This is a thing we're working on, but it's still not working as intended.", than have a repeat of this fiasco. Sure there will still be some mistakes made, but I think that at least a little more transparency would dampen unrest.

It's more or less what I was insinuating with my initial message (don't rush for release, take more time, etc).

PS: I'm not saying this group or this group of people are doing BS.
Show topic
Last visit Tuesday, 23 April 06:10:19 UTC
P_:

powered by ryzom-api