Re: Next 4.6.x stable release, numbering, qemu-tag

[George Dunlap <george.dunlap@citrix.com>]

On 15/06/16 11:46, Jan Beulich wrote:
>>>> 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.

Indeed, that thread did show up in March, and the author said he was
building against 16.04, even though Google tells  me Ubuntu 16.04 wasn't
released until 21 April 2016.  He must have been using a beta release of it.

And unfortunately his report dropped through the cracks.  The fix from
upstream should have been backported to qemu-xen at that point, but it
(apparently) didn't come to the attention of the right people.

"Remember all the things you've forgotten or didn't notice" is about as
actionable as "fix all the bugs you don't know exist". :-)

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel