All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: xen-devel@lists.xen.org
Subject: Proposal: Xen Test Days
Date: Wed, 01 Aug 2012 13:08:30 +0100	[thread overview]
Message-ID: <50191C3E.4050003@xen.org> (raw)

Hi everybody,

at OSCON I had a couple of discussions regarding Fedora-like Xen Test 
Days. It may be a little bit late for this release putting all the 
documentation together (i.e. a TODO list of what we want to community 
and distros which consume Xen) to test to pull this off for this release 
cycle.

But I wanted to raise this as possibility and maybe something to build 
into future release cycles.  If I look at 
http://wiki.xen.org/wiki/Xen_4.2 there is fairly little (or in fact 
almost nothing) we have in terms of how new functionality would be 
tested. My gut feel is that the biggest benefit of a Xen test Day for 
4.2 may be in testing XL. There were some improvements last Monday, but 
I am not sure this is enough.

If I look at https://fedoraproject.org/wiki/QA/Test_Days they have spent 
quite a bit of effort on this, and it would probably take one person a 
week or two full-time to pull this together. Also see, 
https://fedoraproject.org/wiki/Test_Day:Current

I just wanted to put this out there to see whether we should try for 
this release cycle and gather views. It would require a volunteer to 
step up. If the view is that this is not doable for 4.2, this may be a 
good thing to either try for patch releases as well as maybe for Xen 4.3

Regards
Lars

             reply	other threads:[~2012-08-01 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 12:08 Lars Kurth [this message]
2012-08-01 14:50 ` Proposal: Xen Test Days George Dunlap
2012-08-01 16:23   ` Lars Kurth
2012-08-01 19:50   ` Pasi Kärkkäinen
2012-08-02  6:57     ` Ian Campbell
2012-08-02 13:33       ` Lars Kurth

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=50191C3E.4050003@xen.org \
    --to=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.