From: Lars Kurth <lars.kurth@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Russell Pavlicek <russell.pavlicek@citrix.com>, xen-devel@lists.xen.org
Subject: Re: preparing for 4.2.3 and 4.1.6
Date: Fri, 12 Jul 2013 12:18:32 +0100 [thread overview]
Message-ID: <51DFE608.70005@xen.org> (raw)
In-Reply-To: <51DFF51F02000078000E46B6@nat28.tlf.novell.com>
Jan,
I am confident that we can manage driving the test days in between
Dario, Russell and me. It does require a reliable schedule for RC's as
well as a list of bug fixes that we need to highlight as "please test
XYZ for RCx" in the Test Day Description. So there would be some impact
on you in helping pull that info together: but I'd assume that you would
be on top of the delta between say 4.2.2 and 4.2.3, etc. anyway.
Lars
On 12/07/2013 11:22, Jan Beulich wrote:
>>>> On 12.07.13 at 12:05, Lars Kurth <lars.kurth@xen.org> wrote:
>> just asking the question whether you want to build test Days into the
>> 4.2.3 and 4.1.6 cycles.
> Certainly desirable, if it's not going to need to be me to spend
> meaningful amounts of time driving these (which I don't mean to
> extend to the need to deal with eventual fallout - that of course
> I'm absolutely ready to do even if time is otherwise tight).
>
> Jan
>
next prev parent reply other threads:[~2013-07-12 11:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 8:47 preparing for 4.2.3 and 4.1.6 Jan Beulich
2013-07-12 9:17 ` Ian Murray
2013-07-12 9:22 ` Jan Beulich
2013-07-12 9:30 ` Ian Murray
2013-07-12 10:05 ` Lars Kurth
2013-07-12 10:22 ` Jan Beulich
2013-07-12 11:18 ` Lars Kurth [this message]
2013-07-12 13:13 ` Ian Murray
2013-07-12 12:52 ` Don Slutz
2013-07-12 13:06 ` Ian Jackson
2013-07-12 13:53 ` Konrad Rzeszutek Wilk
2013-07-15 17:33 ` Stefano Stabellini
2013-07-17 11:03 ` Ian Jackson
2013-07-15 12:35 ` Daniel Kiper
2013-07-15 12:48 ` Jan Beulich
2013-07-17 11:37 ` Ian Jackson
2013-07-17 11:37 ` Ian Jackson
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=51DFE608.70005@xen.org \
--to=lars.kurth@xen.org \
--cc=JBeulich@suse.com \
--cc=russell.pavlicek@citrix.com \
--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 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).