Field notes
Good releases
start before “run.”
Practical reading for teams maintaining software on someone else’s infrastructure. Written for the handoffs that usually live in tickets and email.
01 / Operations
Updating software on customer-owned servers
Separate release preparation, permission and execution. ↗02 / ControlWhat should a customer actually approve?
Define the exact change before asking for a yes. ↗03 / RecoveryPlan a Docker update before touching production
Images, persistent data and recovery are different jobs. ↗Start with your application
See where your
application fits.
Find out whether your customer hosts and update workflow match Shipstead’s planned scope.
Check compatibilityNo email. No call. Results stay in your browser.