Knowing what is deployed.
WHY IT MATTERS
Without it, nobody can say what is running.
WHAT TO DO
Tag each release in version control Record the deployed version somewhere visible Keep a record of what each release contained
WHAT A TAG PROVIDES
A fixed reference you can return to.
WHAT TO NAME THEM
Something ordered and unambiguous: a version number or a date.
WHAT TO RECORD FOR EACH RELEASE
What changed When it was deployed Who deployed it Any manual steps performed
WHY THAT LAST ONE
Manual steps are forgotten, and their absence causes failures later.
WHAT TO SHOW IN THE APPLICATION
The deployed version, somewhere accessible.
WHY
So you can confirm what is actually running without guessing.
WHAT THAT ENABLES
Correlating an incident with a release Reverting to a known state Answering what changed
WHAT TO AUTOMATE
Tagging, as part of deployment.
WHAT TO KEEP
The record, indefinitely.
