Feature Flag-Driven Development… in Reverse
Talkat OpenFeature Summit NA 2025 · on Monday, 2025-11-10· at 14:45· Building B | Level 2 | B213-214·
summary
Feature toggles become the mechanism for safe removal rather than just launches: Octopus uses telemetry, granular toggles, staged rollouts and CI checks to deprecate features with rollback ability. Usage drove decisions—PowerShell and bash show thousands of uses while one legacy tool shows 20 uses—so small-impact items get a six‑month warning and staged soft deprecation, then hard removal; the platform ships a built-in toggle system with expiry metadata and an auto reset after one week policy that is dogfooded and in alpha, reducing bloat and enabling quick rollbacks.
AI-written summary · about
chapters (10)
- 0:00Feature flag-driven dev in reverse
- 1:04Deprecating features is hard
- 3:55Feature risks: add vs remove
- 5:19Deprecation as controlled demolition
- 7:47Warning phase and toggles
- 9:54Soft deprecation and staged rollouts
- 13:04Hard deprecation and removal
- 16:31Monitoring feature toggles
- 18:36Benefits of deprecation
- 19:17Summary
related talks
01h 09mFeature flags: the toggle, the A/B test and the canary
51mFeature Toggles, or How to Deploy Features Without a Release
41mFeature Flags: Separate Deployment from Feature Release
35mFeature Toggles: The Good, The Bad, and The Ugly
56mWhen Feature flags go bad
40mWhen Feature flags go bad
06mFeature Flag Foul-ups
59mFaster & less risky releases with feature flags