Practise the standard verbs for announcing and tracking API deprecations.
0 / 5 completed
1 / 5
Fill in: 'We ___ an API deprecation notice at least ninety days ahead, rather than a shutdown nobody consuming it's actually prepared for.'
We 'issue a notice' — the standard, simple collocation for formally announcing an API's retirement. The other options are less idiomatic here.
2 / 5
Fill in: 'A deprecation notice buried in a changelog can ___ integrators blindsided by a shutdown nobody's actually seen announced.'
We say a buried notice will 'leave' integrators blindsided — the standard, natural collocation for the resulting disruption. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a sunset date clearly in the notice, rather than a timeline nobody consuming the API's actually pinned down.'
We 'state a date' — the standard, simple collocation for giving a firm deprecation timeline. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every remaining consumer against the traffic logs before shutdown, rather than an integration nobody's actually confirmed migrated.'
We 'check a consumer' — the standard, simple collocation for confirming who's still calling a deprecated endpoint. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ deprecated endpoint traffic weekly as the sunset date approaches, rather than a call volume nobody's actually monitored dropping.'
We 'track traffic' — the standard, simple collocation for monitoring usage of an endpoint being retired. The other options aren't idiomatic here.