Have you ever wondered what makes Debian so stable (even Debian testing)?

Find out what tools and processes are put in place to ensure that everything we ship is of the highest quality and how Debian ends up being the first one to find and report issues to external projects.

There’s a lot to talk about, so we are sticking to the high level and to covering as many items as possible.

The main topics are the release process and the QA/CI/testing mechanisms.

Presenter: Samuel Henrique "samueloph" is a software developer focused on Debian, Linux, Python, Rust and Security. He's a Debian Developer, contributing mostly to packaging of security tools in the Debian Security Tools Packaging Team (pkg-security). Samuel maintains a few other key packages on Debian, such as "curl", "rsync" and "nmap", for which he's also responsible for fixing CVEs for all Debian releases. Working as a System Development Engineer in Amazon Linux, Samuel develops Rust and Python-based systems that deals with CVE processing at AWS. He also helps people learning packaging and starting to contributing to Debian.

Presented on 2024-08-01 at DebConf24: https://debconf24.debconf.org

00:00 Waiting to start 00:05 Intro 01:27 About me 02:21 Summary 03:44 A distribution 04:56 Organization 06:15 Debian releases and special repositories 08:27 20 architectures 09:29 buildd 10:10 Diversity of architectures 11:46 Example of issue on goawk 12:30 Example of issue on aircrack-ng 13:00 Experimental, Unstable and Testing 14:05 Experimental 15:50 Unstable 17:16 Testing 19:24 Stable creation? 20:25 The freeze process 22:01 Stable updating? 23:37 Stable repositories 24:27 The release process 24:57 QA/CI/testing 25:58 dh_auto_test 28:08 lintian 28:51 Example of issue on curl 29:28 Autopkgtest and debci 31:04 debci 35:10 Example of issue on aeskeyfind 36:59 Example of issue on nmap 37:39 salsa-ci 40:13 Honorable mentions 41:35 Questions