Release Process Review

If changes go straight to your live site by hand, every update is a small risk, and the errors land on your customers. This review looks at how changes move from a developer's machine to the public and sets up a process that catches mistakes first.

Who it's for

  • Changes go straight to the live site, with no test environment in between.
  • Code isn't in version control, or not all of it is.
  • Release errors keep reaching customers and take time to fix.
  • You pay for a hosting platform but work around its tools instead of using them.

What I do

  1. Walk through how a change gets from a developer to the live site today, step by step.
  2. Check version control, test environments, caching and who has access to push to production.
  3. Design a release process that fits your team and your hosting platform, with every change tracked and tested.

This review designs the process. It doesn't include migrating your sites or setting up the tooling. If you want help with that work, we can scope it once the plan is set.

What you get

  • A map of your current release process, with the risky steps marked
  • A recommended process, from version control to the live site
  • A short list of caching and performance fixes for traffic spikes

Where this comes from

At a broadcasting company with 7 news sites, we moved from manual releases with no Git and no test environment to a tracked, three-environment process on Pantheon. The team was named one of Pantheon's Best in WebOps Top 20 in 2023.

The Release Process Review is $1,500 (two weeks, for one site or application). If it shows you need more than a review, the 30-day audit or an ongoing engagement is the next step.