Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Software Update 2018.28.1 7d0461c

This site may earn commission on affiliate links.
It would be great if this fixed the iphone X echo problem (over bluetooth). .26 did not.
But that wouldn't be AP rev dependent? Right? Wonder what an AP2.x version is fixing (if that's not a red herring...). (I know all X's are AP2.x, but S's and 3's are getting this...)

upload_2018-8-7_10-31-20.png
 
In the quarter all just a few days ago they stated roll out would begin end of august with wide rollout in september

No, they said it would go to the EAP, Early Access Participants, group at the end of August, and then they hoped to go public with it in September. (They never said wide.)

And if it is 4 weeks until it goes to beta testers it is possible they will run into issues and miss September all-together. (Since almost any delay in their stated schedule would cause them to miss September.)
 
No, they said it would go to the EAP, Early Access Participants, group at the end of August, and then they hoped to go public with it in September. (They never said wide.)

And if it is 4 weeks until it goes to beta testers it is possible they will run into issues and miss September all-together. (Since almost any delay in their stated schedule would cause them to miss September.)
I must have misheard it. Thank you for the info
 
Interesting it's so 'old', since you'd think 2018.30 would have been 'now', at the mininum (this is week 32).
They most likely started merging the new AP and v9.0 from the dev branch to the public branch around week 26-29.

Makes no sense to roll out newer versions now until v9.0 is out. When they do, it's most likely minor changes based of the old 8.1 versions made for unit testing parts of the new code and providing feedback to the mothership without depending on the new code. Introducing new code and testing it gradually in the background for partial roll-outs is a way of reducing risk.
 
  • Helpful
Reactions: croman
They most likely started merging the new AP and v9.0 from the dev branch to the public branch around week 26-29.

Makes no sense to roll out newer versions now until v9.0 is out. When they do, it's most likely minor changes based of the old 8.1 versions made for unit testing parts of the new code and providing feedback to the mothership without depending on the new code. Introducing new code and testing it gradually in the background for partial roll-outs is a way of reducing risk.

If they're using agile practices, and everything points to this, the code has always been merged in master branch/stream and toggled off. What you're seeing (2018.28) is a release with minimum changes as most of the changes/work is happening to the parts of the code which we have in most of our cars (depending on current firmware) but it's completely dormant until DevOps flips the "on" toggle. Just a guess based on following their release notes/what's new and release schedule.