From: Dario Faggioli <raistlin@linux.it>
To: lars.kurth@xen.org
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Building Xen Test Days into the conclusion of the Xen 4.3 release cycle
Date: Thu, 25 Apr 2013 00:14:23 +0200 [thread overview]
Message-ID: <1366841663.9843.73.camel@Solace> (raw)
In-Reply-To: <51769AC6.2000603@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 2357 bytes --]
On mar, 2013-04-23 at 15:29 +0100, Lars Kurth wrote:
> Hi everybody,
>
> I wanted to follow up on George's e-mail (Xen 4.3 development update
> CODE FREEZE at
> http://lists.xen.org/archives/html/xen-devel/2013-04/msg02142.html). One
> way we can facilitate the goal of
>
> 1. Have a bug-free 4.3 release
>
> ... is to build in some Test Days into the coming weeks. This worked
> well for Xen 4.2 RC2 as well as XCP 1.6.
>
+1 ... I really really like the idea of test days!
> What we do need though is a
> good set of test instructions for Xen 4.3 : examples for last time round
> were
> - http://wiki.xen.org/wiki/Xen_4.2_RC2_test_instructions
> - http://wiki.xen.org/wiki/XCP_1.6_test_instructions
> We have a document day coming up next Monday, which would be an ideal
> day to put together Xen 4.3 RC test intrstructions. I remember we got a
> lot of test coverage for 4.2 RC2 as well as XCP 1.6.
>
> Having a predictable schedule around RC's would also help. It appears to
> me that maybe one test day every other week starting from the first RC
> (planned for May 6th would work) ... we could do the test day 1-2 days
> after the planned RC's to provide for a buffer should an RC slip.
>
> That would give us dates for Xen Test Days for May 8, May 22 (not
> clashing with Hackathon), June 5 (with RC's planned 2 days before).
>
Sounds cool.
> Views? Should I start announcing the dates and promote the Test Days?
>
Yes, I think we should. For what I've seen from the 'Fedora Test Days',
the success of the whole thing depends on having people around and
actually following the instructions and running the tests, even if
everyone just do that for a small subset of them!
> If
> so, I need some commitment on getting good Test instructions as well as
> a good sense that RC's are possible for these dates. If so, I would like
> to announce these by the end of this week.
>
I'm going to be on leave next Monday (during DocsDay), but for
everything else you need from May 2nd on, count me. :-)
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)
[-- 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
next prev parent reply other threads:[~2013-04-24 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:29 Building Xen Test Days into the conclusion of the Xen 4.3 release cycle Lars Kurth
2013-04-23 14:53 ` jacek burghardt
2013-04-23 15:04 ` Roger Pau Monné
2013-04-23 15:09 ` Ian Campbell
2013-04-23 15:12 ` Wei Liu
2013-04-23 15:18 ` Lars Kurth
2013-04-24 19:53 ` Stefano Stabellini
2013-04-24 22:14 ` Dario Faggioli [this message]
2013-04-25 7:49 ` Ian Campbell
2013-04-25 8:25 ` Lars Kurth
2013-04-25 11:18 ` Lars Kurth
2013-04-25 14:15 ` George Dunlap
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=1366841663.9843.73.camel@Solace \
--to=raistlin@linux.it \
--cc=lars.kurth@xen.org \
--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 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.