From: Ian Campbell <Ian.Campbell@citrix.com>
To: jaeyong.yoo@samsung.com
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline
Date: Mon, 7 Oct 2013 12:25:08 +0100 [thread overview]
Message-ID: <1381145108.21562.86.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <15784101.232461381142962039.JavaMail.weblogic@epml15>
On Mon, 2013-10-07 at 10:49 +0000, 유재용 wrote:
> > ------- Original Message -------
> > Sender : Jan Beulich<JBeulich@suse.com>
> > Date : 2013-10-07 15:55 (GMT+09:00)
> > Title : Re: [Xen-devel] Xen 4.4 development update -- RFC for feature freeze timeline
> >
> >>>> On 07.10.13 at 06:59, 유재용 wrote:
> >>> On Thu, 26 Sep 2013, George Dunlap wrote:
> >>> > Additional things which are likely to make it if we extend a month (18
> >>> > Nov):
> >>>
> >>> > * NUMA Memory migration
> >>> > * Per-vcpu NUMA affinity
> >>> > * PV NUMA interface
> >>> > * ARM guest migration
> >>> > * USB hotplug for libxl
> >>> >
> >>> * new hypercalls for SWIOTLB on ARM
> >>
> >> I have a question regarding the candidate features for feature freeze.
> >> Can anyone declare a new feature or does it only for Citrix employees and
> >> maintainers?
> >> For instance, if I want to upstream live migration feature in ARM, what am I
> >> going to do?
> >
> >You'd announce (ideally in the feature _planning_ phase) that you
> >intend to work on a particular feature, and if possible give at least
> >a rough estimate when you expect to have things in shape to go in.
>
> Aparently, I have missed the announcement, my mistake.
It's no problem, these things are mostly guidelines, not rules and as
George says the list is just a prediction not a decision, it is entirely
possible for things to go in without having been listed there.
I have your migration patches in my queue to look at, hopefully this
week.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-10-07 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 10:49 Xen 4.4 development update -- RFC for feature freeze timeline 유재용
2013-10-07 11:25 ` Ian Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 10:45 Jaeyong Yoo
2013-10-07 4:59 유재용
2013-10-07 6:55 ` Jan Beulich
2013-10-07 9:53 ` George Dunlap
2013-09-27 11:52 Boris Ostrovsky
2013-10-04 15:59 ` George Dunlap
2013-09-26 16:47 George Dunlap
2013-09-26 17:24 ` Dario Faggioli
2013-09-27 6:21 ` Elena Ufimtseva
2013-09-27 7:38 ` Jan Beulich
2013-09-27 9:37 ` David Vrabel
2013-09-27 9:51 ` Jan Beulich
2013-09-27 7:41 ` Jan Beulich
2013-10-04 17:36 ` George Dunlap
2013-09-27 10:21 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1381145108.21562.86.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=jaeyong.yoo@samsung.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.