Coordinating a Release Print

  • devopsinfrastructure, devops, backup, guide, howto, solution, zillionkinghost, hosting
  • 0

The human side.

WHAT TO AGREE BEFOREHAND

What is being released When Who performs it Who verifies Who to contact if something goes wrong

WHAT TO PREPARE

The change list The rollback plan A message for users, if the change is visible

WHAT TO CHECK BEFORE STARTING

That someone is available afterwards That no other change is happening simultaneously That backups are current

WHAT TO ANNOUNCE

Internally, before and after.

WHAT TO DO DURING

Follow the documented process Record anything unexpected

WHAT TO DO AFTERWARDS

Verify Watch for a period Confirm completion

WHAT TO AVOID

Releasing when key people are unavailable Releasing several things at once to save effort Deciding to proceed despite a failing check

THAT LAST POINT

A failing check is information. Overriding it is how incidents begin.

WHAT TO RECORD

What was released, when, by whom, and the outcome.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot