From: "Mihai Donțu" <mdontu@bitdefender.com>
To: wei.liu2@citrix.com
Cc: elena.ufimtseva@oracle.com, artem.mygaiev@globallogic.com,
quan.xu@intel.com, ian.jackson@eu.citrix.com,
oleksandr.dmytryshyn@globallogic.com, chegger@amazon.de,
edgar.iglesias@gmail.com, cyliu@suse.com,
edmund.h.white@intel.com, Steve.VanderLeest@dornerworks.com,
fabio.fantoni@m2r.biz, Aravind.Gopalakrishnan@amd.com,
chao.p.peng@linux.intel.com, feng.wu@intel.com,
zhigang.x.wang@oracle.com, parth.dixit@linaro.org,
dgolomb@seas.upenn.edu, eshelton@pobox.com,
kai.huang@linux.intel.com, Paul.Skentzos@dornerworks.com,
jtweaver@hawaii.edu, wency@cn.fujitsu.com,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
oleksandr.tyshchenko@globallogic.com, guijianfeng@cn.fujitsu.com,
daniel.kiper@oracle.com, josh.whitehead@dornerworks.com,
anthony.perard@citrix.com, xen-devel@lists.xenproject.org,
manishjaggi.oss@gmail.com, olaf@aepfle.de,
julien.grall@linaro.org, ian.campbell@citrix.c
Subject: Re: Xen 4.6 Development Update (two months reminder)
Date: Mon, 16 Mar 2015 15:01:56 +0200 [thread overview]
Message-ID: <20150316150156.551748aa@bitdefender.com> (raw)
In-Reply-To: <E1YW0FY-0002P7-DJ@ukmail1.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2724 bytes --]
On Thu, 12 Mar 2015 10:21:56 +0000 wei.liu2@citrix.com wrote:
> We are now two months into 4.6 development window. This is an email to keep
> track of all the patch series I gathered. It is by no means complete and / or
> acurate. Feel free to reply this email with new projects or correct my
> misunderstanding.
>
> = Timeline =
>
> We are planning on a 9-month release cycle, but we could also release a bit
> earlier if everything goes well (no blocker, no critical bug).
>
> * Development start: 6 Jan 2015
> <=== We are here ===>
> * Feature Freeze: 10 Jul 2015
> * RCs: TBD
> * Release Date: 9 Oct 2015 (could release earlier)
>
> The RCs and release will of course depend on stability and bugs, and
> will therefore be fairly unpredictable.
>
> Bug-fixes, if Acked-by by maintainer, can go anytime before the First
> RC. Later on we will need to figure out the risk of regression/reward
> to eliminate the possiblity of a bug introducing another bug.
>
> = Prognosis =
>
> The states are: none -> fair -> ok -> good -> done
>
> none - nothing yet
> fair - still working on it, patches are prototypes or RFC
> ok - patches posted, acting on review
> good - some last minute pieces
> done - all done, might have bugs
>
> = Bug Fixes =
>
> Bug fixes can be checked in without a freeze exception throughout the
> freeze, unless the maintainer thinks they are particularly high
> risk. In later RC's, we may even begin rejecting bug fixes if the
> broken functionality is small and the risk to other functionality is
> high.
>
> Document changes can go in anytime if the maintainer is OK with it.
>
> These are guidelines and principles to give you an idea where we're coming
> from; if you think there's a good reason why making an exception for you will
> help us make Xen better than not doing so, feel free to make your case.
>
> [...]
I have been meaning to write this email for a while now, just to let
everyone know we're working on a couple more patches related to VM
introspection. They are not as big as our initial ones, but they do
bring in new functionality.
Răzvan Cojocaru will post a series based on Tamas' changes, as soon as
it stabilizes some more or (even better) gets merged. I'll let him
choose the right moment.
I will also pick up some of my [oldish] patches with reviews from Andrew
and Ian and also try to tackle some of the x86 emulator challenges
that we talked about some months ago. We've adjusted our plans and aim
for a to-the-point set of changes that allow one to built a security
solution (at least) the we envision it, in terms of isolation and
monitoring capability.
Regards,
--
Mihai Donțu
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-16 13:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 10:21 Xen 4.6 Development Update (two months reminder) wei.liu2
2015-03-12 10:54 ` George Dunlap
2015-03-12 11:26 ` Dario Faggioli
2015-03-12 11:34 ` Fabio Fantoni
2015-03-12 11:41 ` George Dunlap
2015-03-12 11:54 ` Jan Beulich
2015-03-12 14:15 ` Aravind Gopalakrishnan
2015-03-13 10:32 ` Ian Campbell
2015-03-16 10:43 ` Wei Liu
2015-03-16 15:58 ` Lars Kurth
2015-03-13 18:05 ` Konrad Rzeszutek Wilk
2015-03-12 12:18 ` Tamas Lengyel
2015-03-12 15:07 ` Ian Campbell
2015-03-12 15:39 ` Dario Faggioli
2015-03-12 15:57 ` Josh Whitehead
2015-03-12 19:25 ` Meng Xu
2015-03-12 16:01 ` Olaf Hering
2015-03-12 16:15 ` Dagaen Golomb
2015-03-12 18:31 ` Daniel Kiper
2015-03-13 8:40 ` Olaf Hering
2015-03-12 18:54 ` Aravindh Puthiyaparambil (aravindp)
2015-03-12 18:59 ` Daniel Kiper
2015-03-13 8:41 ` Olaf Hering
2015-03-13 3:02 ` Chun Yan Liu
2015-03-13 9:44 ` Chao Peng
2015-03-13 17:30 ` Ed White
2015-03-13 18:02 ` Konrad Rzeszutek Wilk
2015-03-13 18:05 ` Andrew Cooper
2015-03-13 18:12 ` Konrad Rzeszutek Wilk
2015-03-16 13:01 ` Mihai Donțu [this message]
2015-03-16 16:00 ` Lars Kurth
2015-03-16 16:18 ` Razvan Cojocaru
2015-03-16 16:51 ` Mihai Donțu
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=20150316150156.551748aa@bitdefender.com \
--to=mdontu@bitdefender.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=Paul.Skentzos@dornerworks.com \
--cc=Steve.VanderLeest@dornerworks.com \
--cc=anthony.perard@citrix.com \
--cc=artem.mygaiev@globallogic.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chegger@amazon.de \
--cc=cyliu@suse.com \
--cc=daniel.kiper@oracle.com \
--cc=dgolomb@seas.upenn.edu \
--cc=edgar.iglesias@gmail.com \
--cc=edmund.h.white@intel.com \
--cc=elena.ufimtseva@oracle.com \
--cc=eshelton@pobox.com \
--cc=fabio.fantoni@m2r.biz \
--cc=feng.wu@intel.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=ian.campbell@citrix.c \
--cc=ian.jackson@eu.citrix.com \
--cc=josh.whitehead@dornerworks.com \
--cc=jtweaver@hawaii.edu \
--cc=julien.grall@linaro.org \
--cc=kai.huang@linux.intel.com \
--cc=manishjaggi.oss@gmail.com \
--cc=olaf@aepfle.de \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=oleksandr.tyshchenko@globallogic.com \
--cc=parth.dixit@linaro.org \
--cc=quan.xu@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xenproject.org \
--cc=zhigang.x.wang@oracle.com \
/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.