Hi everyone, This is the reminder that we are currently in the feature freeze. I apologise for the delay.
I decided to make the code freeze date on Fri Sep 22, 2023, to give people more time to react because of my late reminder about feature freeze. The hard code freeze date will remain unchanged, i.e. Fri Oct 6, 2023. So currently we have 2 weeks before code freeze and another 4 weeks before hard code freeze. If everything goes well, we can cut 4.18 rc1 at Fri Sep 29, 2023. Also, below is the critical items on my list for 4.18 release: 1. [PATCH 0/7] tools: More Python 3 fixes (part 1 of N) https://gitlab.com/xen-project/xen/-/issues/114 2. tools: Switch to non-truncating XENVER_* ops https://lore.kernel.org/xen-devel/20230117135336.11662-1-andrew.coop...@citrix.com/ 3. dom0less vs xenstored setup race Was: xen | Failed pipeline for staging | 6a47ba2f https://marc.info/?l=xen-devel&m=168312468808977 https://marc.info/?l=xen-devel&m=168312687610283 4. The proper eIBRS support for x86 https://lore.kernel.org/xen-devel/ec8e75da-743b-50dc-4665-854c446c9...@citrix.com/ 5. [PATCH 1/2] credit: Limit load balancing to once per millisecond https://lore.kernel.org/xen-devel/20230630113756.672607-1-george.dun...@cloud.com/ 6. [PATCH 0/2] Revoke IOMEM/IO port/IRQ permissions on PCI detach for HVM guest https://lore.kernel.org/xen-devel/20230809103305.30561-1-jul...@xen.org/ 7. [PATCH v2 0/8] Fixes to debugging facilities https://lore.kernel.org/xen-devel/21cc28b9-91d1-1e6e-23ac-00c44f3ec...@gmail.com/ Kind regards, Henry
