1) Create newest firmware changes
2) Test in house
3) deploy to small number (250-500) “test vehicles”
4) watch for bug reports/track diagnostic data
5) if bug then return to (1)
Otherwise....
6) deploy to all applicable cars
@WEST TEX EV: That sound's like a great theory, that isn't what they do for all of the first run builds however. There are multiple examples of them just going all out right from the word go.
Comments
36.2.4 got past 5300 on 12/10 in less than 6 days....
1) Create newest firmware changes
2) Test in house
3) deploy to small number (250-500) “test vehicles”
4) watch for bug reports/track diagnostic data
5) if bug then return to (1)
Otherwise....
6) deploy to all applicable cars
So 40.1.1 seems like a “bug detected” scenario.