Yes, exactly! We have differing things we each would include at the micro level. I can see the macro features being very useful for marketing. Can we have a data sheet of what actually is in the delivery though? Seems like every release there are improvements but we don't know what they are and folks have to decipher them through reverse engineering.
We know these descriptions of improvements should be available. Otherwise how does management know that their developers are actually doing something? I sure would appreciate granular detail in some document that I could access as an owner describing what they did. Something like "AP will now identify the primary car in white and secondary cars in grey with noticed cars in shadow relief, secondary cars are defined to be ones that could become primary" or "AP now detects the primary car leaving the current travelling lane to avoid phantom braking". There are so many.
This kind of granularity would also be helpful to Tesla. Instead of saying something like "we improved the autowipers", and getting responses like "no you didn't". If they told use "we changed autowipers to detect mist and in that situation wipe once per 5 seconds" they would get feedback like 5 seconds is too long or too short. Folks who don't want the granularity can skip it all. But me thinks that this group wants it. Just look at the disappointment voiced each time release notes are too macro to be useful.
