From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Lars Kurth <lars.kurth.xen@gmail.com>
Cc: xen devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen 4.6 retrospective] [good] Feedback from developer meeting Wed 19th : What went well in 4.6
Date: Fri, 28 Aug 2015 16:01:27 +0100 [thread overview]
Message-ID: <55E077C7.2010602@citrix.com> (raw)
In-Reply-To: <55E08F94020000780009DDF1@prv-mh.provo.novell.com>
On 28/08/15 15:43, Jan Beulich wrote:
>>>> On 28.08.15 at 14:28, <lars.kurth.xen@gmail.com> wrote:
>> * Testing: staging and master being close together for most of the cycle
> This was observed or said by whom? I've certainly got - not
> infrequently - a different impression.
I second the query. The 4.6 development period has had two different
occasions when staging and master have been more than a month apart.
The trend is definitely getting worse, not better.
~Andrew
next prev parent reply other threads:[~2015-08-28 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 12:28 [xen 4.6 retrospective] [good] Feedback from developer meeting Wed 19th : What went well in 4.6 Lars Kurth
2015-08-28 14:43 ` Jan Beulich
2015-08-28 15:01 ` Andrew Cooper [this message]
2015-08-28 15:11 ` 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=55E077C7.2010602@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xenproject.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.