Hi Jan, > On Sep 25, 2023, at 14:32, Jan Beulich <[email protected]> wrote: > > On 25.09.2023 03:25, Henry Wang wrote: >> Hi everyone, >> >> This is the reminder that we are currently in code freeze. The hard code >> freeze date will be in two weeks, i.e. Fri Oct 6, 2023. > > Could you further remind us about what is (not) permitted to go in during > this time?
Sorry, my bad. From code freeze, technically only bugfixes and release Blockers can go in. > I also understand all commits need a release ack from now on? I think so. > (I'm sorry, we're doing releases only every once in a while, so it is > always good for things to be re-spelled out, i.e. even if they haven't > changed from earlier releases.) Actually, thanks for asking! For MISRA work... > This, for example, would then likely mean > that all Misra work now needs queuing for after the tree re-opens ... …I also thought about this, to be honest I am tempted to loose the control or at least offer some flexibility on this specific part, as normally MISRA related changes are harmless and actually harden the code. I am wondering if there are any objections from others… Committers, would you mind sharing your opinion on this one? Thanks! Kind regards, Henry > > Thanks, Jan > >> The planned date for 4.18 rc1 is this Friday, i.e. Sep 29, 2023. >> >> Also, below is the (updated) 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/[email protected]/ >> >> 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. [PATCH v2 0/8] Fixes to debugging facilities >> https://lore.kernel.org/xen-devel/[email protected]/ >> >> Kind regards, >> Henry >> >
