[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Feedback for postponing the 4.17 release to a week later
- To: Henry Wang <Henry.Wang@xxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Wed, 2 Nov 2022 08:27:14 +0100
- 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=qA7w3Q/Ft1Hm0JdhOtciqeJDaqXY6ivjvOLkDpiaTMo=; b=aDy8vo/BOnBMr8O/hF0J9/uFvbkEsDML+tCfZdpWueIkQuZ/6+RzX0eLCITTL0iv59Ytjm8UaBw/CAxGZlLnnSRtNeDn2EdbN5s+L4NpwEgcCg11JehIcVOwGj4mwSDvLFZhUBOSEbSBEdS7C6LDcGPL95neQ999lYEvYHVyiFc81+JIk2eB1Lv3qLUdt8qzJ8CODnq+LkvuxWHQ3EIwBzxptNATF4RsfVSEOMRUricPJDOJRKggeD14wwakiVL44LvYXMB72KoDiAaPLcSWKEKWuGT1Ux+emPz3+Q3aww4JaEMHkbuwzH4RANYGa8yZbHVvyO1aZcgO2bqXImn86w==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ThQwZ5lkpPBwFgZ7mJN9EQMCu8CmWMv4f3SqWDOGo3j3xsfi6mqWZsORpW9Xy+tG+KTkSxVwTvvhAg5IGgm7uHnESloNGvxFwTVoDOPxdghoCYtK69iHM/LRkzg8rBI/hyhzKKwjwsTrpWkw7FlITiG04mAgzCmP0DeuybRunj5P2TVowggRizR9Fhxk4dBKcp1MRiH87Z0gcs61bcsw//GMvFc+adurta6Uy9a5F9T1ZwrHPq5RRjhK4RvFZ1j7g0NZE2CkILHDQEolaXlj7W8zscqTaceh2iQK6EpjxB+2nWauELRjIb9P5omq/kPaVx7lknH8+ufhJ268aYtBYQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, "christopher.w.clark@xxxxxxxxx" <christopher.w.clark@xxxxxxxxx>, "christopher.clark@xxxxxxxxxx" <christopher.clark@xxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Julien Grall <jgrall@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>, "sstabellini@xxxxxxxxxx" <sstabellini@xxxxxxxxxx>, "jgross@xxxxxxxx" <jgross@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Wei Liu <wl@xxxxxxx>, "Wei Liu (LSG)" <liuwe@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Julien Grall <julien@xxxxxxx>
- Delivery-date: Wed, 02 Nov 2022 07:27:27 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 02.11.2022 04:00, Henry Wang wrote:
> Hi Julien and Jan,
>
>> -----Original Message-----
>>>> Somewhat related. When should we branch for the release and set
>>>> CONFIG_DEBUG=n?
>>>>
>>>> I think we would at least need a RC with CONFIG_DEBUG=n but IIUC we
>>>> usually do it at a point where the tree is nearly frozen.
>>>>
>>>> AFAICT, there are still a few things in flight (including fix for
>>>> XSA-409). So I am not sure we are in position yet to branch. Any opinions?
>>>
>>> +1 to it being too early to branch. I would suggest that the XSA batch
>>> should have gone in first and release blockers should have been dealt
>>> with (unless for some it is clear that they're going to be unintrusive),
>>> to limit what needs applying to staging and the new branch.
>>
>> I agree, therefore I think we can switch to CONFIG_DEBUG=n in the RC
>> next week after the Nov. 1 XSAs. So we have at least a week after the RC3.
>>
>> Does this sound ok?
>
> Thank you both for the suggestions!
>
> Just in case I forget this...I saw the xenstore XSAs been merged yesterday,
> and hence may I please ask for a clarification if you are ok with the above
> plan so we can tag RC3 this week later after master branch is synced with
> smoke/staging?
>
> Also I think we need to submit a patch to make the default CONFIG_DEBUG
> to n in Kconfig? Thanks!
Iirc what was done in 4.16 was to switch to non-debug immediately after
branching, on the new branch only. That was specifically to keep debug
enabled at all times (and no undue code churn) in staging. Debug
intermediately off was (earlier on) observed to result in huge Coverity
reports, because of the perceived differences in the pre-processed /
produced code.
Jan
|
