Debian releases are known by both a version number and a memorable codename drawn from Toy Story characters — understanding this naming convention and current release status helps you navigate Debian documentation and plan upgrades.
Why Toy Story Names
Debian's release codenames have traditionally been named after characters from the Pixar film Toy Story — a long-standing project tradition dating back many releases, giving each version a memorable identity beyond just a version number.
Recent and Notable Debian Codenames
| Codename | Version | Status Context |
|---|---|---|
| Bullseye | 11 | Older stable release, moving toward end of standard support over time |
| Bookworm | 12 | Current or recent stable release at time of writing |
| Trixie | 13 | Next release in development (Testing) as of this writing |
Always verify current release status directly, since this naturally progresses over time — check Debian's official release information for the current authoritative status.
What "Unstable" Is Always Called
Regardless of the current Stable codename, the Unstable branch is permanently named "Sid" — it doesn't get a new name with each release cycle, since it represents an ongoing rolling development branch rather than a specific versioned release.
Checking Your Current Debian Codename
cat /etc/os-releaselsb_release -cWhy This Matters for Your sources.list
Repository configuration (see How to Manage Debian's APT Sources and Repositories) typically references the codename directly rather than the version number — understanding which codename corresponds to your intended release avoids configuration errors from using an outdated or incorrect codename.
Using "stable" Instead of a Specific Codename (A Trade-Off)
deb http://deb.debian.org/debian stable mainUsing the generic stable alias instead of a specific codename means your sources automatically track whatever is currently Stable — convenient, but means a major version upgrade could happen unexpectedly during a routine apt upgrade when Debian releases a new Stable version, rather than requiring deliberate action; many administrators prefer pinning to a specific codename for more predictable control.
Planning for End-of-Support
Each Debian release has a defined support lifecycle — track your current release's support timeline and plan upgrades (see How to Upgrade Debian 11 to Debian 12) proactively rather than reactively once support has already ended.
Checking Official Current Release Information
Since release status changes over time, always verify current information directly from Debian's official release pages rather than relying solely on potentially outdated documentation, including this guide's specific version references.
Continue Reading
- Debian Stable vs Testing vs Sid: Understanding the Release Channels
- How to Upgrade Debian 11 to Debian 12 (Complete Step-by-Step Guide)
- How to Manage Debian's APT Sources and Repositories
Browse more articles in Debian VPS Tutorials.
