xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: xen-devel <xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Cc: xen-users
	<xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
	"xen-api-GuqFBffKawuEi8DpZVb4nw@public.gmane.org"
	<xen-api-GuqFBffKawuEi8DpZVb4nw@public.gmane.org>
Subject: 5th Xen Test Day for 4.3 is Wed, June 19th! [Was: Re: [Xen-devel] 4th Xen Test Day for 4.3 is Tomorrow!]
Date: Wed, 19 Jun 2013 00:45:21 +0200	[thread overview]
Message-ID: <1371595521.27273.163.camel@Solace> (raw)
In-Reply-To: <1371559572.27273.134.camel@Solace>


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

It is, of course, the _5th_ TestDay, as said in the body of the message,
and not the 4th one, as the subject line is mistakenly saying! :-P

While at it, allow me to say that RC5 test instructions are on-line:
http://wiki.xen.org/wiki/Xen_4.3_RC5_test_instructions

Let me also tell you that, thanks to the great work of Michael Young, we
have some nice Fedora RPMs for Xen-4.3.0-RC5 available here already:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5517793

Regards,
Dario

On mar, 2013-06-18 at 14:46 +0200, Dario Faggioli wrote:
> Hi everybody,
> 
> Allow me to quickly remind you that the fifth and most likely *final*
> Xen Test Day for the 4.3 release cycle is happening _tomorrow_, Wednesday,
> June 19th!
> 
> We will be on #xentest, testing Xen-4.3.0-RC5, which will likely be
> the version that will be released... If you were waiting for the code
> to be stable and close enough to the actual release to chime in and do
> some testing, well, tomorrow is the perfect time then!
> 
> For more information, see:
>  - On Xen Test Days (will point to RC5 test instructions):
>     http://wiki.xen.org/wiki/Xen_Test_Days
> 
>  - On testing Xen in general:
>     http://wiki.xen.org/wiki/Testing_Xen
> 
> See you tomorrow on freenode channel #xentest.
> 
> Regards,
> Dario
> 
> -- 
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel-GuqFBffKawuEi8DpZVb4nw@public.gmane.org
> http://lists.xen.org/xen-devel

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.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: 0 bytes --]



      reply	other threads:[~2013-06-18 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 12:46 4th Xen Test Day for 4.3 is Tomorrow! Dario Faggioli
2013-06-18 22:45 ` 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=1371595521.27273.163.camel@Solace \
    --to=dario.faggioli-sxgqhf6nn4dqt0dzr+alfa@public.gmane.org \
    --cc=xen-api-GuqFBffKawuEi8DpZVb4nw@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 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).