[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Xen 4.18 release: Reminder about code freeze
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Henry Wang <Henry.Wang@xxxxxxx>
- Date: Mon, 25 Sep 2023 07:21:23 +0000
- Accept-language: zh-CN, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.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=9Ls2NwEeUB+Rop6IL5Pgc0Zxn5JPEwYF14Rv6XpxRcA=; b=gRJ64YSOe6cYxSaCWrEz0loht6/JQM2Vo3kINYgShhZTESAEnr5vyYdDC5GWoMFe8Ud3d8IIbbJxof/8l++dskqq7npmp/FxsF9jRpoZsyz+gHdsEu4aEGt1XmVyJQGUzw6bkvZUtaplKOW8xgUpnkIYoHSlVlJHgCxqW5FTbLf0CLmA4eWRRW/HMlm5oxbjL5FDfsM+7VIkNeus1bF6pSMrK/qfKvSOMZnyVtVBsT9U6Dl3Zr2R4v6hYqhd+0rZYUeL7V+mPlhdSeEwL7vngWRpQXEqdY96xARpVmm1yvFSZiLYPG+5tWy1VeZCHZ58BlLM8vUV7Z0pc0E8C1ekSg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JizK7gQPDkkjrmHr78hMryJJzTXzZy3gWCMs/nFgLbRNgsrF8Acp6ZQQ58fSYVV72MChqs9QiWw7fctxU/Cym1oZxyhKMKk24UhC33bUb2F4+j7yineO12HkOMGJUgDLYiEnxsTvZqHD+PfdbP4LYwnhFRQnIBSKYnKUguonNDkEvUm/HnvIAOvLuM7Hn/MtmjQk+ggarofk8xjmSD8UG3xUqsYoMgwQVR7TKipx8LEpk64Y4dyS6UPolwRJayKYh3fhKjYEe27d3pMSD7hx9ZOs8JvQ6f+4iPLdugA/CnQIfKeaBqPTVEmZIEdg/P2aCUMIkiDMsrtI7b750OTaJw==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.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:21:41 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHZ705Dwyrpd4I60kahQfZlaJ2JtLArFXGAgAACIQCAAAmkAIAAAeYA
- Thread-topic: Xen 4.18 release: Reminder about code freeze
Hi Jan,
> On Sep 25, 2023, at 15:14, Jan Beulich <jbeulich@xxxxxxxx> wrote:
>
> 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
Thanks for the list, your proposal sounds good to me and all release-acked.
>
> I'll also commit "MAINTAINERS: Remove myself as RISC-V maintainer", without
> thinking that it would need a release ack.
Sure, of course.
Kind regards,
Henry
>
> Jan
|
