Back to joining the party: It's been end-of-the-year stuff all day, up to and including cleaning the lint out of the clothes drier.Regarding the release notes and how technical they are, I feel like an important point is being missed here about about why they do this.
Tesla engineers write the release notes before the release goes out and gets widely tested. Obviously, they are of limited use to end users that want to know in their actual driving what will be better, is the car more reliable now, where are there changes, etc. I get that and it's a valid complaint.
The problem is you can't answer those higher level questions before collecting data about the actual performance of the system. Part of the point of having such a large group of testers is Tesla can make very specific change (say, increasing the training data set for lane topology perception in snowy conditions), do some initial testing to look for obvious safety issues, ship it to 100k+ cars, and look for improvements at scale in the telemetry they get back.
Maybe the change makes 1% of left turns less jerky; maybe it makes 50% of intersections smoother. I would be really hard to predict precisely how the average user would actually experience these changes - plus it can depend so much on your local road conditions. If this were easy, they'd just tell us and they wouldn't even need a big real world test group.
That's why Tesla gives us a change log of what they changed and their intent with it. It's either that, or vague "Bug fixes and improvements". They don't tell us the impact of those changes, but plenty of Youtubers do if that's what you're interested in.
In a very weird way, I don't mind reading the obtuse, hard-to-decipher release notes. It's clear that whoever it is or they are that are doing it, they know what's going on. They're using the lingo they've invented or manipulated to describe what they're doing. Given the research level of FSDb development, it's likely that the lingo is changing over time, as breakthroughs in method and concepts kick in.
It's kind of like a U.S. person traveling to Australia, going into a bar, and trying to understand what the locals are talking about. The slang and idiom will be obtuse, hard to understand.. but it's got grammar, fits in with words that the listener does know, and, with a little experimentation (and getting laughed at), the listener learns the language. And concepts. And how they fit together.
None of this is a surprise. A little bit of thought reveals that this is how kids learn. Admittedly, we'd all like to have a reference manual to speed up the uptake; but given the flex and weff of what's going on in the software coders' heads, any ref doc so written would probably get obsolete pretty quickly.
So, the release notes currently resemble a firehose: Open wide, and hang on. It's the experts speaking; they're not slowing down (much) for us; but one can glean a fair amount of information each time a collection of notes gets issued.
I've been messing with new technology since I was a high-school student back in the 1960's and was around for the beginnings of the computer age: Programming on an Altair, keypunch and tape punch on local and remote IBM mainframes, soldering on studs and terminal strips to wire wrap to through-hole circuit boards to surface mount and fine-pitch to BGAs and flip-chips. All of the new technology started off in research labs with obtusely written papers; language got changed and pushed down into undergraduate, then high school, and right into elementary school, madly receiving pedagogical improvements as the tech ideas and concepts matured. Frankly, FSDb is just another one of these major hunks of technology coming into common use; complaining about the lingo is exactly like old farts complaining about terms like RAM, ROM, and "double-U-double-U-double-U dot" when the technology got pushed to the masses.
It's the new stuff. Enjoy it and hang on by your fingertips. Your grandkids won't believe you when you tell them about the beginnings .