3 ms·
Quote highlight for any Tesla owners (and friends of Tesla owners) who may be concerned about this. "This issue is fixed in any release >= 2020.4.10." It look
by jka 7y ago
Quote highlight for any Tesla owners (and friends of Tesla owners) who may be concerned about this.
"This issue is fixed in any release >= 2020.4.10."
It looks like this release started rolling out mid-February 2020[0].
[0] - https://teslascope.com/teslapedia/software/2020.4.10 https://teslascope.com/teslapedia/software/2020.4.10
- natch 7y agoYes good to highlight that. Most of us are on 2020.10 or 2020.12 by now.
- chrisweekly 7y agoThose version numbers look way too similar to dates!!
- TheSwordsman 7y agoIt seems to generally follow the format of Year.Version.Patch.
- invisible 7y agoThey are in this format: Year.Week.Patch
- natch 7y agoWhat (user) invisible said. year.week or year.week.patch if there has been a patch. And there's a build number after that. We're on 4fbcc4b942a8, probably the prefix of a git hash I'm guessing. But then there's kind of a marketing version number as well, for which we are currently on v10.0 or v10. something: https://www.teslarati.com/tesla-v10-wide-release-mobile-app-update/ https://www.teslarati.com/tesla-v10-wide-release-mobile-app-... Those versions are more like the true major release versions, whereas the date versions are inside of that and are minor releases.
- chrisweekly 7y agoThanks all, but I wasn't asking for help parsing it, rather critiquing it as a poor version formatting choice bc of its ambiguity.
- natch 7y agoYes that’s a valid critique, and one I agree with. I added my comment more as an elaboration for anyone else interested in more.