From: Dario Faggioli <raistlin@linux.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 TODO
Date: Tue, 24 Jul 2012 17:29:32 +0200 [thread overview]
Message-ID: <1343143772.4998.78.camel@Solace> (raw)
In-Reply-To: <1343040275.4091.13.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1273 bytes --]
On Mon, 2012-07-23 at 11:44 +0100, Ian Campbell wrote:
> Plan for a 4.2 release:
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00793.html
>
> The time line is as follows:
>
> 19 March -- TODO list locked down
> 2 April -- Feature Freeze
> << WE ARE HERE
> When It's Ready -- First release candidate
> Weekly -- RCN+1 until release
>
> The updated TODO list follows.
>
> ...
>
> tools, blockers:
>
> ...
>
> * xl compatibility with xm:
>
> * [BUG] cannot create an empty CD-ROM drive on HVM guest,
> reported by Fabio Fantoni in <4F9672DD.2080902@tiscali.it>
> (Ian C, has a half baked patch)
>
> * does not automatically try to select a (set of) node(s) on
> which to create a VM and pin its vcpus there. (Dario
> Faggioli, first half applied, second half reposted)
>
> and re-reposted. :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-07-24 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 10:44 Xen 4.2 TODO Ian Campbell
2012-07-24 15:04 ` Jan Beulich
2012-07-24 15:29 ` Dario Faggioli [this message]
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=1343143772.4998.78.camel@Solace \
--to=raistlin@linux.it \
--cc=Ian.Campbell@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).