What we learned shipping VS Code weekly (without breaking everything) | BRK204
Pierce Boggan and Joshua Spicer break down how the VS Code team scaled from monthly to weekly releases without letting quality slip, focusing on practical workflows that reduce review bottlenecks, close test gaps, and keep triage under control.
Overview
Shipping faster sounds great until the costs show up in predictable places: missing tests, slower reviews, and a growing backlog of issues and regressions to triage. This Build 2026 session describes the patterns the VS Code team used to make weekly releases sustainable while handling a high rate of change (100+ commits per day).
Key practices covered in the session description include:
Agent-driven working patterns
- Running agent sessions before meetings to get work moving earlier and reduce coordination overhead.
- Turning conversations directly into pull requests (PRs) instead of writing specs first.
Review and throughput improvements
- Addressing review bottlenecks that appear when release cadence increases.
- Using PR-centric workflows to keep changes flowing while still maintaining quality.
Automated triage at repository scale
- Automating triage across one of GitHub’s largest repositories to prevent backlog growth.
- Using automation to keep up with the volume of incoming issues and changes.
Quality safeguards for frequent releases
- Using “harnesses” (quality guardrails) to keep quality high even as commit volume increases.
- Closing test gaps that become more painful as release frequency increases.