Should the app version on the browser be the same as on the mobile device?
Hello,
I've been studying Dronelink Release Notes (by the way, thank you Jim for that) while trying to understand if the app version on the browser should be the same as on the mobile device.
For example, on my Android 12 device, the Dronelink version is 3.3.2 (198), Kernel 3.3.1, but on the Firefox browser the Dronelink version is 3.3.1 (no build number shown), Kernel 3.3.1
The other question that's related to the Dronelink Release Notes, would it be helpful to add a sheet, i.e., one sheet for Release Notes and a 2nd sheet exclusively for Beta? If not, maybe consider just adding a legend to explain that the notes on the current beta version that's in development have a cautionary yellow header, assuming that's in fact the case?
Comments
6 comments
The revision number may not be the same, but the minor and major versions need to be. If you are always on the latest it shouldn't be a problem, and we force upgrades when needed. The main thing that really matters is the kernel version numbers are always in sync, but we also automatically handle that for you.
As for the release notes, I usually mark the top section as beta, but missed it last time. It is updated now.
Thanks for the question as I am lost with all these versions even I am an happy dronelinker : beta, official, minor, major, app, mobile, 3.x.y.
Maybe a small schematic would be appreciated.
If you are not using the beta, then none of this really matters because we have mechanisms in place to make sure you can't go wrong. If you are in the beta, then some of this confusion comes with the territory and you might consider leaving the beta.
Thank you so much for that clarification Jim and for the update at https://docs.google.com/spreadsheets/d/1BhEFrDV7UHM7fDJKq_4kpFbIa3_egmPv10ucvi1BA9c/edit#gid=0
Fully agree with you Jim.
Thing is that Beta posts should be added in "Beta Test Feedback" repo to avoid disturbance.
Moving this to beta.
Please sign in to leave a comment.