1.10.0

Completed
Follow
Neil Young
  • Edited

Since now 1.10.0 has been released, I'm wondering, what kind of update strategy you could suggest. The way, how CloudAPI is deployed, makes it very hard to follow all these changes, because, if you already have advanced in your fork based on a given release, you have to literally compare the official older release with the official new release in order to find the difference, which you have to follow, to be up to date. And if the change is mutual, things get messed up soon

Wouldn't there be another deployment method more suitable? It is nightmarish to do that from one minor release to the next... I really fear the major update...

It is also great to see, that you didn't give any f..ck on bug reports etc (e.g. missing build of release binary in pom.xml, https://github.com/dji-sdk/DJI-Cloud-API-Demo/issues/51,  https://github.com/dji-sdk/DJI-Cloud-API-Demo/issues/54)

1

Comments

3 comments

Date Votes
  • Ma Ka

    Very important input, I'm very interested in that too.

    0
    Comment actions Permalink
  • Neil Young

    Thanksfully, this time only a couple of files have been changed, mostly just version related... But 1.8 to 1.9 was an orgy of renamed files and folders... :)

    I also don't know how this could be done better, honestly...

    0
    Comment actions Permalink
  • DJI Developer Support
    At the moment, the recommendation is to use the Git tool for comparison; there isn't a better alternative for now.
    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post