EOL
End of Life
The version is no longer maintained. You should expect no regular bug fixes, security patches, or compatibility updates.
EOL Glossary and Support Lifecycle Guide
Learn the meaning of EOL, EOS, EOAS, LTS, active support, and security support, then use the checklist to plan safer software upgrades.
Lifecycle Terms
EOS
End of Support
The vendor or project has stopped providing support for that release. In practice, EOS and EOL often require the same migration response.
EOAS
End of Active Support
Feature work and regular fixes have ended, but security fixes may continue for a limited maintenance window.
LTS
Long Term Support
A release stream maintained for a longer period than regular releases. LTS still has a fixed end date.
Active Support
Active Support
The release is still receiving regular fixes and is usually the safest target for production upgrades.
Security Support
Security Support
The release usually receives security fixes only. Plan migration before security support also ends.
How to Read EOL.Wiki Data
- 1. Check the status badge first. Active is the lowest risk, security means maintenance is limited, and EOL means the release should be replaced.
- 2. Review the next EOL date and the lifecycle timeline before scheduling upgrades.
- 3. Use release notes and vendor documentation as the final authority for production migration decisions.
Migration Checklist
Inventory every runtime, framework, database, operating system, and appliance version in production.
Prioritize versions already in security-only support or within 90 days of EOL.
Read release notes for breaking changes, removed APIs, and required dependency updates.
Test upgrades in staging with production-like traffic and rollback steps.
Update monitoring, backup, and incident runbooks after the migration is complete.