Bullet Updates

Bullet Updates. Nikhil, Praval & Ramesh. A bullet flying through a tunnel Description automatically generated.

Problem Statement. Acrobat and Reader have 3-day update cycle Latest updates reach 70-75% penetration in a week ARM Updater waits for App Quit once update is detected.

[Audio] Proposal There could be scenarios where we want updates to reach customers *ASAP* Update contains high value & business critical features Critical security updates (0-day fixes) Fixes for critical regressions Get rid of 3 day wait cycle Mitigate dependency on App-Quit Version A Version B ASAP.

[Audio] Strategy Update Classification – We don’t want all updates to be rolled out at bullet speed because of cost implications. Bullet Updates: Contain business critical features e.g. Gen AI, or 0-days fixes etc. Normal Updates: Monthly/Quarterly features Critical Update Detection Detected by the presence of a Marker file on the server by Updater (can be controlled at run time, with no code changes) This file smaller compared to the manifest file  Negligible download cost Download manifest file Bullet Updates: Download immediately Normal Updates: Download every 3 days i.e. Status-quo What is ARM Manifest? Manifest contains all information about updates. ARM parses this to evaluate if update is available and apply it..

[Audio] Strategy (Contd..) 4. Applying Critical updates on user’s machine Two scenarios: App not running – Apply the patch silently App running – Prompt user about the new update Show a link to the release notes Allow user to quit the application to apply silent updates.