A deprecation notice gives your managed engine's major version an end-of-support date nine months out - what work does that create?

## What the notice actually says A deprecation notice for a managed engine version normally carries three things: the version affected, a date after which it is **no longer supported**, and a statement of what the provider will do when that date arrives. It rarely says anything alarming, which is why it is easy to file. The date is the entire content: it turns a piece of infrastructure you were not thinking about into a piece of work with a due quarter. "End of support" typically means two distinct things, and they matter in different ways: - **No more fixes.** Newly disclosed vulnerabilities in that version stop being patched for you. For a regulated business this is a compliance fact, not just an engineering preference, and it can bite well before anything stops working. - **A forced move.** After the date, the provider is entitled to upgrade the instance itself, usually inside your maintenance window, at a time that suits its fleet rather than your release calendar. ## Why the date is the expensive part The engineering is rarely hard; it is the coordination that consumes a quarter. A realistic programme looks like this: 1. **Inventory.** Find every instance on the retiring version across all accounts and environments. The ones that hurt are the forgotten ones: a reporting copy, a staging instance that a compliance report quietly depends on. 2. **Impact analysis.** Establish what the new major line changes: retired syntax used by a view or a routine, a default your workload relied on, a query whose plan changes, and above all the minimum client library version the application must move to first. 3. **Rehearsal.** Restore a copy of real data, run the upgrade against it, and time it. This is the step that produces the number the change calendar needs. 4. **Application testing.** Point a test environment at the upgraded copy and run the workload, including the batch and reporting paths nobody exercises interactively. 5. **Cutover, with a way back.** Take a restore point immediately before, upgrade, verify, and keep the restore point until confidence is real. 6. **Sweep.** Upgrade the stragglers, and close the inventory, because a single missed instance regenerates the whole exercise next year. In a regulated business each of those steps also produces evidence: an approved change record, a test result, an identified approver. That is why nine months is a reasonable notice period rather than a generous one. ## Rollback is not a downgrade The single most consequential property of this work is that a major upgrade is a one-way door in place. Once the data has been converted, the old engine cannot read it. So the way back is either a **restore of the pre-upgrade backup**, which costs the data written since that backup, or a **copy deliberately kept on the old version**, which costs the effort of keeping it fed. A plan that says "roll back if it goes wrong" without naming which of those two it means does not have a rollback plan. ## Acting early against being forced | | You act before the date | The date passes first | |---|---|---| | Who picks the moment | You, against your release calendar | The provider, inside your maintenance window | | Rehearsal | Done on restored data, timed | None | | Rollback | A restore point taken deliberately | Whatever backup happens to exist | | Application readiness | Drivers and queries tested first | Discovered in production | | Security posture in the gap | Short and deliberate | Unsupported while you argue about priority | ## The organisational trap The notice arrives in a quarter that is already planned, and the date is far enough away that it loses to whatever is shipping. The failure mode is not a team deciding to ignore it; it is nobody being named. The fix is unglamorous: give the notice an owner and a target date roughly a quarter before the provider's, so that slipping is survivable, and put the inventory somewhere durable rather than in the ticket. A deprecation notice handled at the eighth month is the same work as one handled at the second, minus the ability to choose when it happens and minus the ability to stop halfway.