How to deprecate a feature the right way
summary
Concrete plan: convene a cross‑functional working group (product, engineering, customer success) and reverse‑engineer a retirement date from a six month deprecation window, accounting for dependencies and buffer time. Miro rebuilds V1→V2, launches them together, then monitor V2 adoption (client IDs, weekly API calls) and only retire V1 after parity; V1 still awaits retirement. Use semantic versioning rules (breaking changes → major), and follow examples like GitHub’s date‑tied versions and ~24‑month support windows.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:23About the speaker
- 2:46What is deprecation
- 5:19Trust in deprecation
- 8:29Deprecation strategy
- 13:40Miro’s platform deprecation
- 17:50Retirement phase
- 19:57Deprecation policy
- 21:25Deprecation and versioning
- 24:34GitHub’s versioning
- 26:42Semantic versioning
- 30:42Four pillars of deprecation
- 33:11Q&A
