Release Engineering Studio
Versioning, changelogs, and deployment windows treated as a craft—not a midnight scramble.
We rehearse coordinated releases with feature flags, canary notes, and measurable rollback triggers. You keep a living decision log so future-you understands why a knob was turned.
What the syllabus includes
- Semantic versioning lab with automated notes
- Canary checklist mapped to observability signals
- Freeze calendar template with exception paths
- Post-release review agenda (blameless)
- Stakeholder comms snippets in EN for APAC teams
- Pairing session on diffing infrastructure plans
- Capstone: plan a two-service release with mock data
Artifacts you leave with
- Author a release note pack stakeholders skim in under 3 minutes
- Define two rollback triggers tied to metrics you already collect
- Facilitate a 20-minute retro using our provided template
Lead mentor
Oskar Lindholm — Release manager turned instructor; prefers boring deploys.
Duration: 4 weeks · weekends · Format: cohort · Category: applied labs · Level: intermediate
Price (informational): 12,400 THB — see Money-Back Policy for eligibility notes.
FAQ
Simulated traffic only. You design the gates; we do not route real users through student clusters.
Yes—ask for the team bundle in your message. Pricing stays informational until we confirm scope.
Mobile release trains (store submissions) are out of scope; we focus on server-side delivery.
Participant notes
Release Engineering Studio forced us to write down “why we ship Tuesdays” instead of assuming everyone remembered.