From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
LarsKurth <lars.kurth.xen@gmail.com>,
DougGoldstein <cardoe@cardoe.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
committers@xenproject.org,
Anthony PERARD <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: Next 4.6.x stable release, numbering, qemu-tag
Date: Wed, 15 Jun 2016 04:46:37 -0600 [thread overview]
Message-ID: <57614E2D02000078000F5447@prv-mh.provo.novell.com> (raw)
In-Reply-To: <57612E31.5030906@citrix.com>
>>> On 15.06.16 at 12:30, <george.dunlap@citrix.com> wrote:
> On 15/06/16 11:25, Jan Beulich wrote:
>>>>> On 15.06.16 at 12:13, <george.dunlap@citrix.com> wrote:
>>> On 15/06/16 11:04, Jan Beulich wrote:
>>>>>>> On 15.06.16 at 11:35, <george.dunlap@citrix.com> wrote:
>>>>> The version of qemu-xen that was tagged with 4.6 had been through
>>>>> several rounds of RCs, months of osstesting, and even through a slew of
>>>>> builds on Travis (which does build Ubuntu, but apparently just not the
>>>>> bleeding-edge version). I only happened to notice it as I was trying to
>>>>> get patches for raisin for 4.7.
>>>>
>>>> The mere fact that 4.6.0 and 4.6.1 exhibited the same issue (and,
>>>> from what you're saying now, which is different from what I've
>>>> understood before, already did when they were cut) would make
>>>> dealing with the issue a non-release-critical one for my taste. IOW,
>>>> if a new version of Ubuntu showed up after 4.6.1, then fixing the
>>>> issue in 4.6.2 (now 4.6.3) would indeed be rather desirable. If,
>>>> however, that release was around already at the time 4.6.1 got
>>>> cut, then I don't see why this is so urgent a problem to address.
>>>
>>> And this is exactly what happened -- the version of Ubuntu which breaks
>>> is 16.04, which (as the name indicates) came out in April 2016 -- two
>>> months after 4.6.1. :-)
>>
>> In which case I don't really follow what you tried to point out with
>> the first sentence of your earlier reply still visible above.
>
> I should have said, "tagged 4.6.2". My point was, there already was a
> lot of testing done for 4.6.2; the tag was done with all the care that
> can be reasonably expected.
Okay, maybe I'm confused then. I had thought all of this was a result
of the thread titled "compilation fail, xen staging-4.6, vnc.c,
qemu-tradintional issues under ubuntu 16.04", which aiui has its origin
in March.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-15 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57504E0802000078000F1164@prv-mh.provo.novell.com>
[not found] ` <20160602140958.GX5160@citrix.com>
[not found] ` <575A868402000078000F3D98@prv-mh.provo.novell.com>
[not found] ` <22362.38888.298368.190872@mariner.uk.xensource.com>
[not found] ` <22362.40282.345007.208511@mariner.uk.xensource.com>
[not found] ` <20160610110551.GA1807@perard>
[not found] ` <22362.40839.475210.399639@mariner.uk.xensource.com>
[not found] ` <575ACFC902000078000F3F49@prv-mh.provo.novell.com>
[not found] ` <22362.47886.957478.714311@mariner.uk.xensource.com>
[not found] ` <575AEA4802000078000F3FC8@prv-mh.provo.novell.com>
[not found] ` <22362.58894.967258.687430@mariner.uk.xensource.com>
2016-06-14 17:57 ` Next 4.6.x stable release, numbering, qemu-tag Ian Jackson
2016-06-14 19:27 ` Konrad Rzeszutek Wilk
2016-06-15 8:57 ` George Dunlap
2016-06-15 9:51 ` Jan Beulich
2016-06-15 7:38 ` Jan Beulich
2016-06-15 9:03 ` Wei Liu
2016-06-15 9:56 ` Jan Beulich
2016-06-15 10:21 ` Wei Liu
2016-06-15 9:35 ` George Dunlap
2016-06-15 10:04 ` Jan Beulich
2016-06-15 10:13 ` George Dunlap
2016-06-15 10:25 ` Jan Beulich
2016-06-15 10:30 ` George Dunlap
2016-06-15 10:46 ` Jan Beulich [this message]
2016-06-15 11:46 ` George Dunlap
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=57614E2D02000078000F5447@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=committers@xenproject.org \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth.xen@gmail.com \
--cc=sstabellini@kernel.org \
--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 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).