Recently, quite a few employees and internal testers have leaked images of Tesla’s release notes. Tesla prefers to keep its software releases and release notes closely held, and they’re now taking some steps by watermarking release notes to prevent further leaks.
Watermarks
In-vehicle release notes will now be watermarked with vehicle VINs. This will prevent quick and simple photos of the release notes from being leaked easily. The presence of a VIN watermark means that an employee or tester who shares an image can be quickly and easily identified and then removed from the testing program.
Tesla is also watermarking the release notes in the Tesla app in addition to the ones in the vehicle.
Tesla is hoping that this will reduce information sharing and prevent leaks. However, there are several ways around this that will likely be used going forward – expect images to be edited after being taken to remove or blur out the VINs, or for the notes to be fully transcribed into text.
Wave 1 Employees
Tesla’s Wave 1 employees receive updates several weeks before they go out to the general public. Wave 1 employees serve as an additional internal testing step, and benefit from the employee perk of early access to new features and improvements. This lets Tesla give its employees a tangible benefit, while also allowing it to test outside its dedicated quality assurance group of employees and vehicles.
This is a pretty crucial role – Wave 1 employees act as a safeguard against buggy updates. By catching potential issues with various vehicle hardware combinations or edge cases here, Tesla can nip these problems in the bud. For instance, the 2024.20 update has already had a revision – 2024.20.1, before starting to go out to Tesla owners. FSD V12.4 is the same – V12.4.1 is likely the version that will be going out to owners.
This is a safety-conscious approach that lets Tesla test for bugs across its widely varied hardware and rectify any bugs as they’re caught by employees. Once no major issues are found in the wave 1 group, either by employee reporting or by automatic bug reports, the update then gradually starts to roll out to the public in small numbers.
