On 02.12.2022 10:16, Jan Beulich wrote: > On 02.12.2022 10:11, Andrew Cooper wrote: >> On 02/12/2022 08:26, Jan Beulich wrote: >>> On 01.12.2022 14:20, Andrew Cooper wrote: >>>> On 28/11/2022 10:50, Jan Beulich wrote: >>>>> All, >>>>> >>>>> the release is due in a couple of weeks time; ideally we'd get it out >>>>> before the year end break. >>>>> >>>>> Please point out backports you find missing from the respective staging >>>>> branch, but which you consider relevant. >>>> I have a whole pile, all to do with (o)xenstored live update, but >>>> they're sadly in my pending 4.18 branch. >>>> >>>> Hopefully there's time for those to get into staging before it's too >>>> late to include for 4.16.3 too. >>> I see you've pushed a bunch; I can't guess though which ones you would >>> intend to be backported. Depending on the size of the set I may end up >>> asking you to take care of cherry-picking. And of course I'll assume >>> the oxenstored maintainers agree with whatever set is intended to be >>> backported. >> >> Yeah - very fortunate timing yesterday. The answer is all of them, plus >> some scattered earlier fixes which did manage to get into 4.17, and even >> some subsequent ones which are still pending for review. >> >> The major bugfix is keeping /dev/xen/evtchn open, and the preceding 8 >> patches are all part of that fix, but "not losing the critical >> information when things go wrong" is important too. >> >> Perhaps it would be easier for me to prepare the backports when the time >> comes? > > Well, yes, "all of them" certainly was what I was fearing when saying > "depending on the size of the set". So yes, please take care of the > backporting once they've passed the push gate on staging.
You will want to have this done the latest by the end of next week, ideally a little earlier, so we can get the release out early in the last week before the year end break. Jan
