I don't get the seeming anger over people's confusion with Lucid's OTA release numbering scheme. Most people are not software engineers, so when they are exposed to a numerical inconsistency for the first time, they are bound to be confused. I, like many of us, have been there in past instances, so I'm sympathetic when some newcomers are scratching their heads. It's a teaching/learning opportunity!
Totally understand confusion and unfamiliarity. We've all been there.
The problem is when people insist they are correct when they are clearly just not informed.
Or when they don't read the explanations that have been posted hundreds of times before posting their own snarky incorrect response.
And then after they've been responded to with a full explanation they continue to argue.
But point taken. It's always harder to see when you are on these forums day in and day out that some folks just don't read this stuff as carefully as we do.
I guess we don't know what went (behind the scenes) between 2.4.4 and 2.4.10.
Correct. At least two possibilities.
There were, in fact releases numbered 2.4.5, 2.4.6, 2.4.7, 2.4.8, and 2.4.9 already. None of which were released to the public. But they were test releases to the internal team, so they need to remain.
OR, Lucid uses the .10 release to signify something specific, such as ".10 is the release number we use for the one that puts everyone back on the same number after we send a couple of different versions to certain cars for various reasons." Or ".10 is always the final bug release for any minor version."
I suspect the latter is the case with Lucid. They seem to specifically use .10 a lot.
