SW 2.0

[Rogue]

I'm lost here. Can you decode this for me? Why would the numbering skip? Does it signify something about the nature of the updates?

The version numbers position signify significance. Writing this comment I cannot remember if there was ever a third number in the OTA. If there was, was it ever not 0? With it being the third number changing, it is the closest to the engineering build. Thus, the shipping may mean it is represented by some internal engineering build number.

All we can do is guess.

 

[DJL]

Pretty amazing. I just received the update notice and my car is at the detailer now getting the PPF applied. It is secured for the night so I just started the update for 2.02. Whoo Hoo!.

 

[Bobby]

Just finished. As promised, no perceptible differences. Excited for the next few!!

 

[HC_79]

I'm lost here. Can you decode this for me? Why would the numbering skip? Does it signify something about the nature of the updates?

Many versions can be committed and not see the light of day externally because a bug is identified before public release and it goes back to the dev team. They fix, commit again on a new version number. This isn’t uncommon to not see sequential version numbers make it to public. It’s a good thing.

 

[NoseyReporter]

One of many big moments for all you brave early adopters. Enjoy it. In a few years you'll all look back and joke about being on v1.x.x when some dingus starts complaining about v33.x.x

 

[martinmeyer]

Many versions can be committed and not see the light of day externally because a bug is identified before public release and it goes back to the dev team. They fix, commit again on a new version number. This isn’t uncommon to not see sequential version numbers make it to public. It’s a good thing.

I’ve seen many software build setups where a version has to be “tagged” before the final build, and building precedes a final QA inspection. If the build fails or final QA fails, the build is discarded and the public may never see that version released at all. That’s likely why 2.0.0 wasn’t seen, and 2.0.1.

 

[thecodingart]

I'm lost here. Can you decode this for me? Why would the numbering skip? Does it signify something about the nature of the updates?

it’s called Semantic versioning. Beyond that knowledge, no need to worry about the exact meaning of the numbers.

 

[groundhog]

Downloaded 2.02 as well.
The new journey begins…

 

[Demosthenes]

2.02 at 3% and counting!

 

[SM_NCarolina]

I'm didn't receive the notification

 

[borski]

Earlier testers had 2.0.1, 2.0.4, 2.0.7. It seems you guys are getting 2.0.2, 2.0.3, 2.0.5, 2.0.8; the version numbers are increased, presumably because of feedback from the earlier testers, and I presume eventually we earlier testers will also get bumped to 2.0.8.

 

[SDHacker]

I'm didn't receive the notification

Did you send a DM and request to be one of first 100 to get the new release as specified in another thread? If not, you might see it in the next couple of weeks. If you did send a DM and got a response that you were in, then there's a problem.

 

[SM_NCarolina]

Earlier testers had 2.0.1, 2.0.4, 2.0.7. It seems you guys are getting 2.0.2, 2.0.3, 2.0.5, 2.0.8; the version numbers are increased, presumably because of feedback from the earlier testers, and I presume eventually we earlier testers will also get bumped to 2.0.8.

Is this still not general release?

 

[Bobby]

Earlier testers had 2.0.1, 2.0.4, 2.0.7. It seems you guys are getting 2.0.2, 2.0.3, 2.0.5, 2.0.8; the version numbers are increased, presumably because of feedback from the earlier testers, and I presume eventually we earlier testers will also get bumped to 2.0.8.

So I wonder what the timeline will be. One per day?

 

[SM_NCarolina]

Did you send a DM and request to be one of first 100 to get the new release as specified in another thread? If not, you might see it in the next couple of weeks. If you did send a DM and got a response that you were in, then there's a problem.

Oh I never saw that message

 

[hmp10]

2.02 at 3% and counting!

You won't see any changes in the operation of your car with 2.0.2. It's a platform update to prepare the car for coming updates that the user will be able to see and use.

 

[borski]

Is this still not general release?

Nope.

 

[RichMalden]

FYI, just finished my update and it was over LTE because I didn't feel like waiting for wifi in the morning and still only took an hour. Maybe it did pre-download and just takes the hour to install.

I do have a strong LTE signal though. The other updates I'll probably do over wifi.

 

[TakeDuo]

FYI, just finished my update and it was over LTE because I didn't feel like waiting for wifi in the morning and still only took an hour. Maybe it did pre-download and just takes the hour to install.

I do have a strong LTE signal though. The other updates I'll probably do over wifi.

Same experience for me. Did mine over LTE while waiting at soccer practice and just under an hour. It started to rain and I immediately regretted the decision realizing I was locked out of the car. Good reception in SoCal though.

 

[hydbob]

Same experience for me. Did mine over LTE while waiting at soccer practice and just under an hour. It started to rain and I immediately regretted the decision realizing I was locked out of the car. Good reception in SoCal though.

Rain in socal?!?!