On Sat, Aug 9, 2014 at 11:56 AM, Rohit Yadav wrote:
> Hi Daan,
>
...
> Yes, I think 4.4.0 was the worst release ever, but that my opinion.
I have only been in on it since 4.1 and only 4.3 hasn't needed a .1
from the get go.
> I faced some (production) issues around KVM, LXC, systemvm, agent and s
Hi Daan,
On 09-Aug-2014, at 9:14 am, Daan Hoogland wrote:
> On Fri, Aug 8, 2014 at 11:48 PM, Rohit Yadav
> wrote:
>> (vacation perhaps?)
>
> You've got my number, yes we can wait. But how different is 4.4.1 from
> 4.4.0 and how much more testing do we need? We can keep postponing
> releases fo
On Fri, Aug 8, 2014 at 11:48 PM, Rohit Yadav wrote:
> (vacation perhaps?)
You've got my number, yes we can wait. But how different is 4.4.1 from
4.4.0 and how much more testing do we need? We can keep postponing
releases for ever. Do you feel the present quality is not up to par? I
think it is as
Hi Daan,
May I suggest if we can take the next week to test 4.4 branch rigorously and
fix bugs, also get some participation from dev and QA folks in the community,
4.4.0 release IMO could have found some more attention from the community. I
just request to do it right this time. In case you’re
That's alright, and it turned out all right. I'm just nervous whether
I can make a 4.4.1 on sunday.
On Fri, Aug 8, 2014 at 11:11 PM, Rohit Yadav wrote:
> Hi Daan,
>
> Sorry about that, my frivolous fix broke the systemvm build job and that led
> series of brute force fixes.
>
> On 08-Aug-2014, a
Hi Daan,
Sorry about that, my frivolous fix broke the systemvm build job and that led
series of brute force fixes.
On 08-Aug-2014, at 10:26 pm, Daan Hoogland wrote:
> H,
>
> Please stop committing to 4.4 the coming time. If there are things to
> make a branch with the following name structure:
