Hi, I have worked out the last big blocker for this migration now. That is, to allow the build on wolkenstein, which is happening via the parts/7release-notes script in webmaster-team/cron git repo.
I forked that repo and committed my changings there: https://salsa.debian.org/holgerw/cron/-/commits/master?ref_type=heads Tests were successful, the results can be found on https://people.debian.org/~holgerw/release-notes_sphinx/www.debian.org/, in the exact same structure as they would appear on the Debian website. The release-notes dir https://people.debian.org/~holgerw/release-notes_sphinx/www.debian.org/releases/trixie/release-notes/ holds the html files for all languages, but content negotiation does not work there apparently; and the apache server does not show a file browser view for that directory. You can find German for example via https://people.debian.org/~holgerw/release-notes_sphinx/www.debian.org/releases/trixie/release-notes/index.de.html or Dutch via https://people.debian.org/~holgerw/release-notes_sphinx/www.debian.org/releases/trixie/release-notes/index.nl.html And remember, there is only one generic variant for all archs now! The build process in 7releases-notes is now different between stable and testing: stable is still on docbook, and testing is on sphinx/ reStructuredText. So, when the time comes, we could create a bookworm branch for r-n, migrate master to sphinx, and activate the build on wolkenstein for master/trixie. That way, we have a comfortable test time, to get everything ready on the website (Note: there are changings to do on the website then), while the r-n for trixie are not in public attention. So long Holger -- Holger Wansing <hwans...@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
