ElGuano said:landonkk said:After a few months of trying to initialize a response, It has now been three weeks since we first heard back from DJI and they sent out the beta. That is plenty of time to get the fix implemented and released to the public if they were working diligently on it. It is clear they are not.... at least not as fast as we should be demanding to accomplish our original goal!
I don't have a dog in this fight (I don't get the hook and have one of the first videos of a P1 showing straight flight in a high-dec location), but I did want to chime on the statement above. I work directly with multiple teams on public facing web and mobile services, software and operating system launches, and the above cannot be farther from the truth. Software release management is complicated process, and what seems like a simple change on the outside more often than not has multiple dependencies and cascading effects, all of which need to be carefully designed, documented, and tested against, including unit, integration and/or regression testing, verification and validation, etc. And this is just standard industry practice, not even taking into account a scenario where a failure could end up endangering or destroying property or causing physical injury. And this error is geographically-distributed and variable as well, meaning iterative changes require coordination of testing and validation across global regions.
I'm not saying it's wrong to push a manufacturer to prioritize a fix, but IME the statement above is inconsistent with basic release management methodologies for software or embedded systems.
We are talking communist China here where not that long ago the management of change procedure read something like this "if you don't get it right we are going to take you out back and shoot you"
I have witnessed even here where a company claims to be state of the art and their systems were laughable