On 11/9/18 11:07 AM, Juergen Gross wrote: > On 09/11/2018 11:56, George Dunlap wrote: >> On 11/9/18 10:16 AM, Juergen Gross wrote: >>> This email only tracks big items for xen.git tree. Please reply for items >>> you >>> would like to see in 4.12 so that people have an idea what is going on and >>> prioritise accordingly. >>> >>> You're welcome to provide description and use cases of the feature you're >>> working on. >>> >>> = Timeline = >>> >>> We now adopt a fixed cut-off date scheme. We will release about every 8 >>> months. >>> The upcoming 4.12 timeline are as followed: >>> >>> * Last posting date: December 14th, 2018 >>> Last posting date for patches touching ARM code: December 1st, 2018 >>> * Hard code freeze: January 11th, 2019 >>> Hard code freeze for patches touching ARM code: December 21st, 2018 >>> * RC1: TBD >>> * Release: March 7th, 2019 >>> >>> Note that we don't have freeze exception scheme anymore. All patches >>> that wish to go into 4.12 must be posted no later than the last posting >>> date. All patches posted after that date will be automatically queued >>> into next release. >> >> Sorry, do you mean "...must be posted no later than the hard code freeze"? >> >> Previously "Last posting date" has meant that as long as v1 was posted >> before that date, vN can be checked in any time before the hard code >> freeze. Just checking to see that that's still the meaning. > > That's the wording used for the last couple releases.
Yes, and I'm sorry I haven't been paying very keen attention; I did this time because I have something I may want to get in. :-) > What about: > > "All patches that wish to go into 4.12 must be posted initially no later > than the last posting date and finally no later than the hard code > freeze." Yes, I think that's more clear, thanks. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
