[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Xen 4.18 release: Reminder about code freeze
- To: Henry Wang <Henry.Wang@xxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Mon, 25 Sep 2023 09:14:24 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=DH3rbZ+u+EVzKUssKuqq/xr3hL9vtQ66aSQ3cCrbWwI=; b=RLUsk/zaQxg5xrN4tnCWJ7B0oSNRED4Rs/rPRDfFuuO3ySmzJjLTQa993xCKIlOhUjNUHIpNSwHHDKvcz/HIbS4gYTxYGGGq39lFrQoEFilFTMbaby1u2KSeR+Mtvthih3LkodOZY7dRbt0y2mcdlP0joPVDDH5Eq6bK1sAwKM2A6xIfIXpgWoUUm5/MlCTlbykCEVBviEX1a7kY2Hilu6Spj7DxrTlZL/FqZSnqof6nAMP93VdxzEH3MmXg0RUztxYSBLWmoRm9XfSfkkkWP+4vvjtl3Z+/Zlih8rKYMdVJPouUgMU8P7jUFh2v+cFlAQ42MRVYPEazeWcoOUL9rQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DN5tKtWhYSCofPNrLdTdyaQkId0L0C4TmMTTS+jsUQ7Y/dmtes2neLTfRgaNnDW4BcnX/U9cMxW/BBxXXovwR6KSWAGavZz/e+iINZEdmvBJd4t2CVeeyCuMcXftl2RIe3uZSZGSl+qda5iWGtInCEIdLlCoML0JKpaPhtg4lGRVTtxMijjLFRuDq9dXZgAmeaona4O52wc+i6/iJu3l4FQ7sATKQyDN9J/AXoylPLbFX83bshB9XVDAX26/e5H57jebK+cZ3qEgLWejqcYkJ+kMosbmObunx6WTBx+8zyqiKFKwkPwQjVbVkl9Wasgn3nyZp6F78Vo6fYq+3IuCeQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: Julien Grall <julien@xxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, "sstabellini@xxxxxxxxxx" <sstabellini@xxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, "jgross@xxxxxxxx" <jgross@xxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, "community.manager@xxxxxxxxxxxxxx" <community.manager@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>
- Delivery-date: Mon, 25 Sep 2023 07:14:39 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 25.09.2023 08:40, Henry Wang wrote:
> Hi Jan,
>
>> On Sep 25, 2023, at 14:32, Jan Beulich <jbeulich@xxxxxxxx> 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…
On a case by case basis, still allowing some in might be okay. You will want
to release-ack them, though. Right now I have three pending for commit which
might qualify:
xen/numa: address a violation of MISRA C:2012 Rule 8.3
xen/hypercalls: address violations of MISRA C:2012 Rule 8.3
xen/emul-i8254: remove forward declarations and re-order functions
I'll also commit "MAINTAINERS: Remove myself as RISC-V maintainer", without
thinking that it would need a release ack.
Jan
|
