Known dates. Structured support. No surprises.
Every release carries published General Availability, End-of-Sale and End-of-Life dates. Lifecycle is a policy, not an email you get one day. This is the strongest single "we will be here" signal a vendor can put on the web.
Version support matrix.
| Version | GA | End of Sale | End of Life | Status |
|---|---|---|---|---|
| v2.1 | 2026-Q3 | — | — | Current |
| v2.0 | 2026-Q1 | 2026-Q4 | 2027-Q3 | Maintained |
| v1.x | 2025 | 2026-Q2 | 2027-Q1 | Sunset |
Dates are the published lifecycle structure. Exact quarter boundaries are confirmed in the lifecycle document, which carries a version ID and date.
General Availability
A release is GA when it is production-supported. New sales and full support run from GA.
End of Sale
After EoS a version is no longer sold to new customers but remains fully supported for existing ones.
End of Life
After EoL a version receives no further updates, including security fixes. Upgrade before EoL.
Plan upgrades against a known calendar.
The lifecycle document is versioned and dated, in the Cisco controlled-document tradition.