Versions & Lifecycle

Debian version choice is not only about freshness. It also depends on the security support source, software stack, hardware support, team maintenance capacity, and upgrade window. This page expands /versions into a lifecycle decision guide.

Current Recommendation

Lifecycle Overview

Version Timeline

Debian 13 regular security support and LTS end dates follow the current public information on the Debian Releases page. If Debian changes them, update this page and the content freshness gate together.

Core Component Comparison

For exact package versions, use packages.debian.org. Do not switch the whole operating system just for one package version until you have evaluated backports, containers, language runtime managers, or the application's own release channel.

Stable, Oldstable, Testing, Or Sid

stable

Best for most users. Package versions do not receive frequent major upgrades, and security fixes arrive through the Debian Security Team and point releases. Servers, office computers, classrooms, and home services should start with stable.

oldstable

Good for already deployed systems that cannot migrate immediately. Oldstable is not "bad", but it should not be the first choice for new deployments. After the LTS transition, support may not cover every package, so check whether your dependencies are in the LTS support scope.

testing

Useful for preparing for the next Debian, checking hardware support, giving feedback, and contributing. Testing receives faster package changes, but its security-update path is different from stable and is not suitable for critical workloads.

unstable (Sid)

Designed for Debian developers and package maintainers. Sid receives continuous new packages and transitions; users should understand apt transactions, dependency recovery, rollback, and bug reporting.

Upgrade Decision Table

Pre-upgrade Checklist

Before changing APT sources:

1. Read the target release notes, especially major changes, removals, and known issues.
2. Back up /etc, user data, databases, service configuration, and local scripts.
3. Confirm the current system has no half-configured packages.
4. Record third-party repositories, pinning, manually installed .deb files, and locally built software.
5. Check disk space, especially /, /boot, and /var.
6. Prepare a maintenance window and rollback path for servers.
7. For remote machines, confirm console, KVM, rescue image, or cloud snapshot access.

cat /etc/debian_version
apt update
apt list --upgradable
dpkg --audit
apt-mark showhold
df -h
find /etc/apt -type f -maxdepth 3 -print

Maintenance Rhythm

Related Pages

• Release End-of-Life (EOL)
• Debian 14 (Forky)
• System Upgrade Guide
• Debian Latest News
• Debian official release information
• Debian LTS