Somebody has to keep Joomla's code base in shape. Bugs fixed, dependencies current, old code taken out, patches reviewed. That is the Maintenance Team, and almost none of it is visible from the outside.
Maintaining the code base is the job. It is ongoing work, independent of any release cycle: it does not start with a version and it does not finish with one. Fixing what is broken, keeping the dependencies current, holding code quality steady and taking out what has had its day. Reviewing pull requests and assessing feature requests is part of that, not the whole of it — and what ships in which release is the Release Team's call, not ours.
This session opens that up. We show what maintenance looks like in practice: how a pull request gets from opened to merged, what makes one sit around for two years, and what we actually look at when we assess one. Then we do the work live: Joomla 7.0 is the release where the things we have been warning about for years finally come out. Previous sprints already removed over a hundred deprecation notices and there is plenty left.
We write code. We review code. We delete code. Mostly the last one. Bring a laptop and a working development setup. We will bring the deprecated code.