< T247045 (stretch->buster) | No task yet (bullseye->bookworm) >
Bullseye preparation work was handled in https://phabricator.wikimedia.org/T275873 and it has been released since.
Debian 11 brings various new features described here: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-whats-new.en.html#newdistro
This task can be used to track long term plans of SRE sub teams (by means of sub tasks). If you run into a specific issue with Bullseye, please don't add it here.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| set target quarter for miscweb bullseye upgrade to 2023-1 | operations/puppet | production | +1 -1 |
Change 900463 had a related patch set uploaded (by Dzahn; author: Dzahn):
[operations/puppet@production] set target quarter for miscweb bullseye upgrade to 2023-1
Change 900463 merged by Dzahn:
[operations/puppet@production] set target quarter for miscweb bullseye upgrade to 2023-1
@Muehlenhoff Where does deploy* (deployment_server role both prod and wmcs) fit in? Since we are still on buster there. But want bullseye deployment_servers in cloud VPS projects and production hasn't upgraded the role yet. A legit subtask for here?
These huge meta tasks are not erally useful, they only end up causing avalances of notifications for little gain. The list of OS updates is being tracked by https://os-reports.wikimedia.org/buster.html (under team breakdown)
Ok, fair enough about the tracking task. But don't we still need some kind of task that someone can take to do the actual upgrade work? So all the subtasks without the tracking parent task?