On 16.11.23 12:03, Julien Grall wrote:
+ JuergenOn 16/11/2023 07:52, Jan Beulich wrote:All,Hi Jan,may I ask on what basis the xen-RELEASE-4.18.0 tag placement was chosen? It matches the 4.17 ones, despite there having been new commits from Jürgen dating back to January / February. (My own build fix would have been nice to have, too, but I can see how that came late.)Before the tagging, the last time we updated to MINIOS_UPSTREAM_COMMIT was in July 2022 (see below).When I prepare the release, I don't have steps to check this is the latest Mini-OS. Instead, I use the commit in the tag.I believe this is the responsibility of whoever decide to add a commit in Mini-OS to also make sure Config.mk is updated accordingly.Anyway, we never tested Xen 4.18 (even before RC) with the new Mini-OS. So I don't think it is sensible to update it at this stage of the release. But I would suggest to send a patch to update Config.mk so the problem doesn't re-occur for 4.19.
I wanted to do this after my current pending Mini-OS patches have been added to the tree. Juergen
OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
