From: Lars Kurth <lars.kurth@xen.org>
To: xen-users@lists.xen.org,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Xen Test Day - Thank You!
Date: Wed, 15 Aug 2012 16:55:47 +0100 [thread overview]
Message-ID: <502BC683.6060407@xen.org> (raw)
Hi,
I wanted to thank everybody who joined yesterday's test day for
contributing. At the peak we had about 30 people on the #xentest
channel, and a number of bugs were raised as well as items were added to
the Xen 4.2 TODO list / Release Plan. There has also been quite a bit of
discussion on the channel.
It appears that measuring the success of the test day is a little harder
than that of docs days. For example, I don't quite know how many tests
were successful as nobody posted success reports to the mailing list.
This makes me think that maybe this is the wrong approach and that we
need to put more prep work into preparing test days.
Here are a number of ideas:
1) Fedora Test Days are much more prescriptive (i.e. test cases are
pre-defined and results are recorded in a big spreadsheet)
2) Maybe we should guide testing a bit more than we have
3) Maybe reporting results should be easier (e.g. a simple web form or a
google docs spreadsheet)
Anyway, suggestions and feedback is very welcome!
Best Regards
Lars
reply other threads:[~2012-08-15 15:55 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=502BC683.6060407@xen.org \
--to=lars.kurth@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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 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).