[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen 4.10 Development Update
On 20/07/17 17:57, Manish Jaggi wrote: Hi Julien, Hello Manish,I am not sure why piggyback on Daniel Kiper as it is not related to your work... On Mon, Jul 17, 2017 at 02:26:22PM +0100, Julien Grall wrote:This email only tracks big items for xen.git tree. Please reply for items you woulk like to see in 4.10 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 twice a year. The upcoming 4.10 timeline are as followed: * Last posting date: September 15th, 2017 * Hard code freeze: September 29th, 2017 * RC1: TBD * Release: December 2, 2017 Note that we don't have freeze exception scheme anymore. All patches that wish to go into 4.10 must be posted no later than the last posting date. All patches posted after that date will be automatically queued into next release. RCs will be arranged immediately after freeze. We recently introduced a jira instance to track all the tasks (not only big) for the project. See: https://xenproject.atlassian.net/projects/XEN/issues. Most of the tasks tracked by this e-mail also have a corresponding jira task referred by XEN-N. I have started to include the version number of series associated to each feature. Can each owner send an update on the version number if the series was posted upstream? = Projects = == Hypervisor == * Per-cpu tasklet - XEN-28 - Konrad Rzeszutek Wilk * Add support of rcu_idle_{enter,exit} - XEN-27 - Dario Faggioli === x86 === ... and answer on x86 category when your items look ARM specific. I am working on XEN-70, have already posted rfc. [1] Also can you please add a xen-jira issue for the ITS ACPI support [2] v2 patches, which I have already sent and am working on next rev. This is already existing in Jira. See XEN-75.But as said at the beginning of the e-mail, this is only tracking big features. We can't possible track all small items as the mail would become too long. I don't consider the two features you mention as big and don't see the need to track them here. But they are already tracked in Jira. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |