NI0Z пишет:
Really my point is this, suggesting a downgrade is a horrible response, it actually seems perfectly valid. What would you expect the response to be taking into consideration that it's new functionality and clearly isn't working like they thought? How fast do you think they can fix that and how large a,programming staff do you think they have? Maybe that's a way to bring clarity to this because I have not had a rude response from Yuri before, he's always been polite and highly responsive. One has to keep in mind different languages and cultures as well. So what was the expected response, then maybe EE can learn something from this?
Hers what I would like to see:
EE create a BETA user group and subsite and invite friendly beta users who can sniff out bugs and report them in an offline area.
If EE is to offer Betas, then denote which one is stable and which ones are not deemed stable and qualify the risks of using an unstable release.
Maybe elaborate more on responses, I.E., please excuse the current issues, we are working on them and if you need working software then please downgrade to the most current Stable release until the features you want are marked as complete in a stable release.
Keep a list of known issues by release and dentote open issues in each release.
Always make sure in all stable releases that core functionality is validated as functional
Use the agile methodology and make more releases with less functionality, we get things faster that way.
What else folks can we tell them?
