All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth-LM2mM/qkH7s@public.gmane.org>
To: xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
	"xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
	<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
	"xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
	<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Subject: Fedora 16 Virtualization Test Day!
Date: Wed, 14 Sep 2011 14:28:40 +0200	[thread overview]
Message-ID: <4E709DF8.6060702@xen.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]

Hi,

as you may know, Fedora 16 will have full Xen support for Dom0 and DomU 
in it. Fedora is planning a number of test days 
<http://fedoraproject.org/wiki/QA/Fedora_16_test_days> as part of their 
release cycle, including a *Virtualization Test on September 15th this 
year*, which is tomorrow.

We are calling our community member to participate in the test day 
tomorrow: certainly many of us here at the Xen Hackathon in Munich 
<http://blog.xen.org/index.php/2011/05/19/xen-hackathon-munich-13-15-september/> 
are planning to do so. As always every extra volunteer who wants to help 
is very welcome.

Information about the virtualization test day can be found here 
<http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization>. We 
will have some people hanging out on IRC at #fedora-test-day 
<http://webchat.freenode.net/?channels=#fedora-test-day> and you can 
also get in touch with us via the usual channels. We should also have a 
test plan ready by later today, which should help you with the testing.

Have fun!

Lars


[-- Attachment #1.2: Type: text/html, Size: 1414 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



                 reply	other threads:[~2011-09-14 12:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E709DF8.6060702@xen.org \
    --to=lars.kurth-lm2mm/qkh7s@public.gmane.org \
    --cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    --cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    --cc=xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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.