The number of source packages in each Debian release (stable, testing, unstable and experimental) is illustrated below. Note that removals from experimental do not necessarily happen automatically when the package in experimental is superseded by a package in unstable.

Package numbers in each release

Source packages may be updated with a new Debian revision (1.2.3-1 → 1.2.3-2) or a new upstream version (1.2.3 → 1.2.4). The number of source packages that have an updated package between releases is show below. Note that:

Updated packages

New upstream versions rather than just new Debian revisions tend to me of more interest to end users. New upstream revisions tend not to be uploaded to unstable during a freeze as there is essentially no chance of them being included in the upcoming release but having them present means that packages that pick them up as dependencies cannot migrate to testing to fix bugs. Note that packages adding an epoch (1:) to their version or repackaging the upstream source and adding a marker like +dfsg to their version (perhaps to remove non-free material like RFCs or sourceless binaries) will also look like "new upstream" versions in this metric; however, there aren't that many such changes.

New upstream versions

Over time, new upstream packages are added Debian. In the Debian context, new packages are ones that a source package name that does not exist in the archive already. New packages can be:

New source packages

These analyses were prepared by Stuart Prescott and make use of the data in #debian's Ultimate Debian Database and queries based on the work of Raphaël Hertzog.

source code data

Data last updated: 2014-09-02