dji-p3p1
lvl.4
Flight distance : 534970 ft
Australia
Offline
|
Hi Bladestrike.
Please take this post as honest and constructive..., as my intent (of many years professional experience in the management/software industry) is to help.
Whilst I fully appreciate there may be some level of testing that DJI conduct on fw/saw releases, I (and many other users) remain unconvinced at how thorough and tightly controlled on filtering issues and bugs it is.
Time and time again, and time again and again, the first few that are brave (or ignorant) enough to do an upgrade are either presented with serious issues or hidden/stealth functionality in new updates, that are not documented or declared anywhere. ( just do a quick search on this and the Phantom Pilots Fourms for plenty evidence of this statement)
I have been asking for a detailed release notes that include known issues, accompanying all releases, a practise followed by most mature companies/development orgs. So that end users can intelligently decide on an update, and at the same time cover DJI in ensuring that known issues are clearly articulated and explained . - it's a win-win situation, for both DJI and the customer, for very little effort.
I appreciate that DJI as a company has grown very quickly, and sometimes critical SDLC steps may be left out whilst an organisation works to fulfil market demand, balance customer needs and address issues.
However DJI is moving away from being a "toy" manufacturer, to providing a platform that many professionals are already starting to use as a serous platform. Sooner or later it is going to have to be far more transparent and following a fully documented and tight Development Lifecycle will be required as it progresses to the next stage. Adopting this practise sooner rather then later will really ease the pains and frustrations of both the users and developers.
|
|