From: tim Doyle <tim@quantact.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: 3.0.3 Status/Schedule
Date: Sat, 08 Jul 2006 22:20:39 -0700 [thread overview]
Message-ID: <44B09227.8000608@quantact.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D572008@liverpoolst.ad.cl.cam.ac.uk>
Great, I'm looking forward to the next release.
Many thanks for all your hard work!
-Tim
--
Timothy Doyle
CEO
Quantact Hosting Solutions, Inc.
tim@quantact.com
http://www.quantact.com
Ian Pratt wrote:
>> Subject: Re: [Xen-devel] Re: 3.0.3 Status/Schedule
>>
>> Any word on the status of the next release?
>>
>> Looks like lots of [PATCH] activity on the mailing list.
>> Getting close?
>>
>>>> The current plan is to shoot for 3.0.3 in the 2nd week July, which
>>>>
> fits
>
>>>> in with the FC6 schedule, and ahead of many developer's trips to
>>>>
> Ottawa
>
>>>> for OLS.
>>>>
>
> We've been talking a lot to the RH folks about what features they'd like
> to see in the FC6 release and when their freeze dates are, and decided
> to hold the tree open a couple of weeks longer.
>
> There are a number of significant patches quite close to being ready for
> inclusion. Several area already getting quite a bit of testing
> out-of-tree, so integration shouldn't be too painful.
>
> * new qemu-dm device model patch
> * PV framebuffer support
> * blktap support for qcow and raw files (and possibly dm-userspace)
> * possibly new shadow pagetable code
> * possibly the NUMA page allocator patches
>
> Best,
> Ian
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2006-07-09 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 23:30 Re: 3.0.3 Status/Schedule Ian Pratt
2006-07-09 5:20 ` tim Doyle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-14 3:17 Horms
2006-07-08 22:36 ` tim Doyle
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=44B09227.8000608@quantact.com \
--to=tim@quantact.com \
--cc=xen-devel@lists.xensource.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.