Hi, Salvatore Bonaccorso <carnil@debian.org> (2025-06-05): > I would like to upload the next version of the 6.12.y stable series to > unstable (once linux/6.12.30-1 migrates to testing). There are two > upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31 > was of considerable size (note there is onging merge window for 6.16 > ongoing and from experience the first few stable series are bigger > than usual, this might not be the best timing for trixie). (Yeah, at this point it seems wise to let .30 migrate.) I don't have a precise timing for the next d-i release (there are things to consider which I have little control over), but given we're getting deeper and deeper into the freeze, maybe we're closer to the point where we should anticipate stopping kernel uploads, and staging them for publication via either trixie-proposed-updates (once 13.0 is published) or DSA depending on the security impacts? Anyway, at this point, still no objection to an extra upload. > We know that for beeing ready for trixie we need to find yet a > solution for > https://salsa.debian.org/kernel-team/linux/-/merge_requests/1524 (and > to allow multiple uploads of one upstream version for instance if we > need to pick a single fix for security reasons and needs to be pushed > earlier than the next upstream stable version). Oh, new challenges. G'luck! Just out of curiosity: there is no plan to change what the versioning looks like in bookworm(-proposed-updates) or bookworm-security, right? Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature