Holger Wansing <hwans...@mailbox.org> (2021-07-30): > And regarding your comment > > - Documenting what isenkram-autoinstall-firmware does means we should > > check what happens for each major release, to keep up with the > > current implementation. Doing that once every two years doesn't seem > > unreasonable though. > > Maybe we can add a 'what-to-check-before-next-stable-release' file for the > installation-guide somewhere, to make sure this does not get forgotten ... > > I think there is such doc somewhere for other artefacts of releasing d-i?
Sorry, I didn't answer that at the time but: d-i.git has scripts/post-release-checklist.txt which is a very quick braindump from a while ago. Maybe we should have a top-level “doc” directory with some more information, like stuff to do at the beginning, during, and at the end of a release cycle. Or those files can be kept under “scripts/”… as long as people wanting to read about such things find the relevant file(s)! Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
