Non-extendable: a date that can only arrive
A non-extendable date is one a vendor states cannot be pushed back on request. It closes a conversation many teams assume they can have, and it is the more plannable position: a date that might move is a date nobody schedules against. As of 2026-09-22.
| Removed by the statement | Made possible by it |
|---|---|
| Any route to an exception | A calendar entry that can be trusted |
| Negotiation by a large customer | A migration sized once, not repeatedly |
| Hope as a planning input | Communicating the date to clients |
| Ambiguity about a passed date | Automated checks with a known deadline |
Inclusion rule. Read from the lifecycle policy of the one platform in this register that publishes such a statement. Order. What the statement removes first, then what it enables.
1It reads as unhelpful and plans better
Most enterprise documents leave room for an exception, on the assumption that a large customer will eventually ask. Stating plainly that dates do not move is unusually direct and it removes an input that was never reliable.
A production that knows the day is fixed can put the migration in a calendar. A production hoping for an extension carries the work as an open worry instead.
2The opposite statement exists in this register
One maker describes its dates as the earliest a model might be retired, which means they can quietly become later. Those two sentences look similar and produce opposite plans.
One supports a calendar entry; the other supports a migration held in readiness for an unknown length of time. Reading both as the same kind of commitment plans two migrations wrong.
3Fixity matters more than length
Thirty fixed days can be scheduled. Six months that might close after a fortnight of disuse cannot. Length and predictability are separate properties of a window and they do not travel together.
The two publishing platforms read against each other show the trade clearly, because they differ on both properties at once.
A definition rather than a dated entry: no line above is a vendor statement. Where this word turns up in a real notice, the wording and the date are on the fixed-date reading. Nearby terms: Model version, Version alias, Version pinning.