[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xen 4.16: Proposed release manager and schedule


  • To: Ian Jackson <iwj@xxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 24 Aug 2021 15:59:00 +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-SenderADCheck; bh=0lTmn+nddLtdKPfdjcVWcHzcdMCrTixfQcjZr4C2DZo=; b=S70CXJoflBvWheExtCPoxen3s1OC7jqw1PpGoHw5RaC3QhsJ8YxbC2M7Z36fLAyjQh2AJhit/Nd/31PIaHvnOZFY/jmkf/K+G6elnyi31d+Wekns19dIY/r2UG0cvdUj1OibXkBnyVh03kobJCI3vrpqOUQis5yk5ZQmPfWaPPDgeK+yNMPSJS6T2YeuyNozEQJl/utrJ0irL5fY0r4pHinB9/+DaM0nMkkqfKLyl4ET3aB2kid/sm4xP0OeOly5NcahPkcwMEh6Vpubn2eii4/RR3897OYrAS/CK8skvIfVcC4xF9K/uPDxXUXo8gs7hvzeLq/QWdnUytkqCCPGOQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U4k6Df32ZFhESLExCy15voowe+uIZHnK7KLxjDnnA4TVwjJu/iRFRCmrHYIrv6D89Q6VdQlvEBml2ZCj7UxaTMbGnzvdboPuA0w5FA4gyzQ5LVCNB/nLBawi5konZLlI/oP885P3Z7AU1/WYaKB+ba157Z0ZNIIdmaaC2kHm6aoo+lsdcbXCEoFOV5Ay0AI2OA5QmC0USkGZ3xqNHd6jHYXFIRa3XVF4WvCLSIqPdHlzDK+BWXshQBFt+2RW+/wff48NZkFCApfcJqnBVSh/Qy3k/HXcW6R0M1vN9dVBrYxJVgu8bX/KXRQzRU5H/SfDCiv7A9LrFMGya1SBv/Fi5A==
  • Authentication-results: xen.org; dkim=none (message not signed) header.d=none;xen.org; dmarc=none action=none header.from=suse.com;
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, George Dunlap <George.Dunlap@xxxxxxxxxx>, committers@xxxxxxxxxxxxxx, Julien Grall <julien@xxxxxxx>
  • Delivery-date: Tue, 24 Aug 2021 13:59:16 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 24.08.2021 15:38, Ian Jackson wrote:
> Julien Grall writes ("Re: Xen 4.16: Proposed release manager and schedule"):
>> On 19/08/2021 16:36, Ian Jackson wrote:
>>> One option is to slip the whole release, in the expectation (hope!) of
>>> collecting more input.  In practical terms because of the impact of
>>> Christmas and New Year on many of our contributors, a month's slip now
>>> is probably more like two months' slip to the release.  So arguably
>>> for this to be worth it, we ought to plan to slip 2 months now and
>>> release in February.
>>
>> A 2 months slip looks appealling to get more features. But it means we 
>> will end up to split all the future releases.
> 
> No, it wouldn't, really.  Our usual release interval is 9 months.
> 9+2 = 11, so the result would be a one month longer release, if we
> delayed this one by 2 months.  In practice it is always a bit of a
> struggle to keep things to time (that's the way things are set up with
> this system) so I think this is well within our usual tolerances.
> 
> For the avoidance of doubt, I am not arguing in favour of this option.
> But I wanted to present it as a reasonable option the community might
> want to consider.
> 
> Jan, do you have an opnion about this ?  Do you expect that a 2-3
> month slip would help with your review backlog, bearing in mind the
> people who are currently on leave and when they'll be back ?

It's extremely hard to predict whether 2-3 months would help, or by
how much. I wanted to make the "slim" release aspect explicit, but
I didn't mean to question the schedule unless there would have been
signals that many care about a more "feature rich" 4.16.

>> At the moment, my preference is to stick with the release in December. 
>> We don't have major contributions checked in yet on Arm, but there is a 
>> chance to have a couple of them with the current schedule on Arm.
>>
>> We also have a collection of bug fixes which makes Arm running better on 
>> some platform.
>>
>> So I think the release would still be worthwhile even in the worst case 
>> where nothing major is merged.
> 
> Thanks for the opinion.
> 
> 
> Can I at least get a +1 from someone for appointing me as RM
> for 4.16 ? :-)

Sure: +1

Jan




 


Rackspace

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