#progressive-delivery
Tagged “progressive-delivery”
4 articlesProgressive rollouts are solved. The validation gate isn't.
A New Stack opinion argues that progressive rollouts are a solved problem while the validation step that actually gates them is still hand-built. From an on-call chair, that reframing is overdue.
Jul 18, 2026 · Maya OkonkwoIncident responseAWS teaches its DevOps Agent to flip feature flags during incidents
The AWS DevOps Blog details an integration where the AWS DevOps Agent's MCP server talks to LaunchDarkly so an agent can identify and toggle the flags relevant to a live outage instead of paging three teams to do it by hand. The integration removes a real coordination step, and forces every shop to write down which actions an agent is allowed to take unattended.
Jun 20, 2026 · Tomás VegaPlatform engineeringWhen async agents outnumber humans, code review stops being the verification layer
A piece in The New Stack picks up Ido Pesok's disclosure from Cognition that more Devin runs are now triggered asynchronously, by events, schedules, automations and other agents, than by people. The argument: once the trigger ratio flips, verification has to move out of code review and into the runtime that CI/CD owns.
Jun 17, 2026 · Priya NairDeployment strategiesFeature flags vs canary deploys: teams are using both, deliberately
The progressive-delivery debate has matured. The emerging consensus isn't 'pick one', it's flags for behaviour, canaries for infrastructure, with clear ownership for each.
Jun 10, 2026 · Priya Nair