[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>, "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>
  • From: Henry Wang <Henry.Wang@xxxxxxx>
  • Date: Mon, 25 Sep 2023 06:40:06 +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=5dzeIPvVU4WWTITOfMKectdXicpkMBPQfetlDL/n6dI=; b=QOszFlzhAVisrvMU8Sb9GQcGOtKrMEhVp2yywzBcNoFyE0p7aMMnDUHRv+3GXyPCEixvztOHgCBMY9yE6rjgbGdHOKaGZS9hHMhMhSGiTeXyAFirEj8dxuU+npvD1X2XMw2JZ9WA23hK5/v+MpFsS+z88xCH+S/9KyFyyMfSTy1crZ2EPfZIWpwNSkekXct0vFK5p90wZOryaQjCcwjdhrG0i6AbAqeFo0/CXij1YTWbud9y2vz908sGutVJV7B2rN60R5NKVE15BGY4zRCslqTLaXqObyH4C0xFHYE3MjBwG840d5O7XG2ZNqGqg49H79XEqoAxg5DEvJukivbZvw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dqIWMTFgfFDs6v+UlEntKv6vQ4QH3DnxZT/H0WZE4HPc614WIRBBokDLyN+8PEzK6KC3gwvf/c9+YHP2Wigdj0F29OgIiwhXCFOX898Tenu7w1xLUY+wLRXPDakE5OaHlKTSm8NvHSW3b200uYB+jyqRLi52ZIg8YIxNtXAKB9ce3NDE1puwpM9/raoYoKoWwUY8ZUbVcQWx+/JoAX9mA2pQvmjAo83GmA4h5wihKxMpOK2sj306/qSoA93FnvOBYGyrLrUGM5BP/VsucNogdylQ95dkMR1SHc1ZBz89rk9ZXdwp8Ml6NwBLXZxFUPg1HnSKlYTNOQ6r5cSUCLf8sw==
  • 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>
  • Delivery-date: Mon, 25 Sep 2023 06:40:34 +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: AQHZ705Dwyrpd4I60kahQfZlaJ2JtLArFXGAgAACIQA=
  • Thread-topic: Xen 4.18 release: Reminder about code freeze

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…

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/20230117135336.11662-1-andrew.cooper3@xxxxxxxxxx/
>> 
>> 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/21cc28b9-91d1-1e6e-23ac-00c44f3ec08e@xxxxxxxxx/
>> 
>> Kind regards,
>> Henry
>> 
> 


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.