From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
Russell Pavlicek <russell.pavlicek@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>
Subject: Re: RC today or Monday or something ?
Date: Fri, 7 Nov 2014 12:50:10 +0000 [thread overview]
Message-ID: <545CC002.80905@citrix.com> (raw)
In-Reply-To: <280C1E5B-BBC8-4E62-9702-86B16E25103B@oracle.com>
On 07/11/14 12:27, Konrad Rzeszutek Wilk wrote:
> On November 7, 2014 6:59:57 AM EST, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 07/11/14 11:37, Ian Jackson wrote:
>>> Russ mentioned that he was expecting us to have a test day next week.
>>> Is that still on; do you want to cut an RC soon ? If you let me know
>>> ASAP we can still do that today, I think.
>>>
>>> Ian.
>> Frankly, tagging an -RC2 before OSStest moves staging into master would
>> leave almost no delta between RC1 and RC2, and leave all of the pygrub
>> bugs still open.
> Good point!
>
>> My XenServer testing of all of this is currently on c/s 5c8dd034 (the
>> change to the MAINTAINERs file for hvmloader) and looking fine.
>>
> Thank you for keeping the tests warm..
It is no problem at all. At the moment, it is literally just a git pull
and wait several hours for basic automatic testing to get back to me and
say "everything still fine".
I suppose it is worth stating that there are no outstanding patches for
bugs I am aware of. All the bugs we have discovered have their fixes in
staging.
~Andrew
next prev parent reply other threads:[~2014-11-07 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:37 RC today or Monday or something ? Ian Jackson
2014-11-07 11:58 ` Konrad Rzeszutek Wilk
2014-11-07 11:59 ` Konrad Rzeszutek Wilk
2014-11-07 12:58 ` Russell Pavlicek
2014-11-07 11:59 ` Andrew Cooper
2014-11-07 12:27 ` Konrad Rzeszutek Wilk
2014-11-07 12:50 ` Andrew Cooper [this message]
2014-11-07 14:16 ` 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=545CC002.80905@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=russell.pavlicek@citrix.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.