[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Timing around last updates for src:linux targetting bookworm



Hi

[Cc'ed explicitly Ben and Cyril]

With the planned release date for 2023-06-10 and dates around that as
announced by the release time it's time to clarify some last work for
src:linux to be targeted for bookworm.

The base details are in
https://lists.debian.org/debian-devel-announce/2023/04/msg00007.html
The full freeze date will be on 2023-05-24. Additionally we need to
take into account the Debian d-i plannings by Cyril and debian-boot.

Foremost, Paul Gevers stated in https://bugs.debian.org/1034446#14
what is okay and for how long:

> I'm pretty sure I've mentioned this to you before, but to be clear to
> everybody I'll state it in public here: we currently trust the kernel
> maintainers to make the right decision until (around) the full freeze
> under the condition that they consider the following:
> 
> * would you propose the same for a point release?
> * if activity in the archive on the d-i front is ongoing or expected
>   check with d-boot.

That means, I still would like to merge the next stable releases. The
latest point, depending on d-i planning would probably be sometime in
the week of the 15th may for a last upload targetting bookworm.

Given the merge window for 6.4, and 6.4-rc1 upcoming, the stable
releases following that are quite big, and I fear we should skip those
for bookworm initial version, meaning we need to stop before that.

Preliminary work on this is at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/707 (at
time of writing updated up to 6.1.27 upstream).

Additionally to that there are some requests which are still okay to
be included for bookworm:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/710
which Ben already stated to be wanted in bookworm.
HW support from Aurelien in 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/711

Open is how we handle #1033058. We added the patch from Cyril, but
this got rejected upstream. I think it would be better to not diverge
for too long from upstream, but AFAIK there was no progress on "the
real fix". Should we revert but then have a regression for the ppc6el
installer? Would that be affordable given the non-graphical installer
AFAIU still works? Cyril, what is your prefered take on this?

One question is how to handle (if some arise) severe security fixes
needed for src:linux in the time were we should not upload. I was
thinking if necessary to use bookworm-security for this already then
and not influencing any d-i work further. Cyril, what do you think? It
is really meant just in case we *need* to have an update, my prefered
way would be to not have to. What about updates with ABI bumps?

So in short: I propose (depending on concrete d-i plannings) to make
last possible upload latest in the week of 15th May. Open is what we
still would like to include.

Are we yet missing anything crucial for the release?

Opinion, comments, acks or nacks or specific items?

Regards,
Salvatore

Attachment: signature.asc
Description: PGP signature


Reply to: