From: Jaeyong Yoo <jaeyong.yoo@samsung.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline
Date: Mon, 07 Oct 2013 10:45:06 +0000 (GMT) [thread overview]
Message-ID: <5782083.232351381142705090.JavaMail.weblogic@epml15> (raw)
>------- Original Message -------
>Sender : George Dunlap<george.dunlap@eu.citrix.com>
>Date : 2013-10-07 18:53 (GMT+09:00)
>Title : Re: [Xen-devel] Xen 4.4 development update -- RFC for feature freeze timeline
>
>On 07/10/13 05: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?
>
>So first of all, "Citrix employee" is absolutely irrelevant to any
>discussion. Committers are chosen based on their merit, contribution to
>the community, and need, according to the Xen governance proceedures
>(http://www.xenproject.org/governance.html). Everything else is just a
>matter of influence. If you want something to happen, just try to
>convince people that it would be a good idea. The more you have
>contributed, and the higher the quality of your contribution, the more
>weight your preferences and judgement will have; but if your idea is
>good and your argument is persuasive, you will be able to convince
>people even with little prior involvement. Citrix employees are on the
>same ground as everyone else -- if they haven't contributed much, they
>won't have much influence.
>
>Secondly, the long list that I send out is just an attempt to track what
>people are doing, so that we have an idea who is doing what, and what
>state the different features are in, so that we can make good decisions
>about when to make releases. It's really just book-keeping. Anyone can
>submit features to be tracked; you just have to respond to one of the
>e-mails, and then respond again with updates when I send it out again.
>
>The list above is an attempt to *predict* what features *will be
>accepted*, not an attempt to *decide* what features are accepted.
>Features are accepted when the maintainers / committers think that they
>are ready. What I am trying to do is help the community decide when to
>do a release. If you think a specific feature worth delaying the release
>for, just try to make a case.
>
>Finally, it sounds like the feature you are talking about is already on
>my list of things which may be worth delaying the feature freeze for a
>month: "ARM guest migration". :-)
Thanks a lot for the explanation.
Now, I've got the clear idea how do I make a feature contribution.
I was worried that I may missed something for upstream the feature,
and I'm relieved that the feature is on your list. :-)
Thanks again,
Jaeyong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-10-07 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 10:45 Jaeyong Yoo [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 10:49 Xen 4.4 development update -- RFC for feature freeze timeline 유재용
2013-10-07 11:25 ` Ian Campbell
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=5782083.232351381142705090.JavaMail.weblogic@epml15 \
--to=jaeyong.yoo@samsung.com \
--cc=george.dunlap@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).