Debian always has at least
three releases in active maintenance:
stabledistribution contains the latest officially released distribution of Debian.
This is the production release of Debian, the one which we primarily recommend using.
stabledistribution of Debian is version 11, codenamed bullseye. It was released on August 14th, 2021.
testingdistribution contains packages that haven't been accepted into a
stablerelease yet, but they are in the queue for that. The main advantage of using this distribution is that it has more recent versions of software.
testingdistribution is bookworm.
unstabledistribution is where active development of Debian occurs. Generally, this distribution is run by developers and those who like to live on the edge. It is recommended that users running unstable should subscribe to the debian-devel-announce mailing list to receive notifications of major changes, for example upgrades that may break.
unstabledistribution is always called sid.
Release life cycle
Debian announces its new stable release on a regular basis. Users can expect 3 years of full support for each release and 2 years of extra LTS support.
Index of releases
- The next release of Debian is codenamed
testing— no release date has been set
- Debian 11 (
bullseye) — current
- Debian 10 (
buster) — current
- Debian 9 (
oldoldstablerelease, under LTS support
- Debian 8 (
jessie) — archived release, under extended LTS support
- Debian 7 (
wheezy) — obsolete stable release
- Debian 6.0 (
squeeze) — obsolete stable release
- Debian GNU/Linux 5.0 (
lenny) — obsolete stable release
- Debian GNU/Linux 4.0 (
etch) — obsolete stable release
- Debian GNU/Linux 3.1 (
sarge) — obsolete stable release
- Debian GNU/Linux 3.0 (
woody) — obsolete stable release
- Debian GNU/Linux 2.2 (
potato) — obsolete stable release
- Debian GNU/Linux 2.1 (
slink) — obsolete stable release
- Debian GNU/Linux 2.0 (
hamm) — obsolete stable release
The web pages for the obsolete Debian releases are kept intact, but the releases themselves can only be found in a separate archive.
Integrity of the data in the releases
Data integrity is granted by a digitally signed
file. To ensure that all files in the release belong to it, checksums of
Packages files are copied into the
Digital signatures for this file are stored in the file
Release.gpg, using the current version of the archive signing
oldstable an additional signature is
generated using an offline key specifically generated for a release
by a member of the Stable Release Team.