[ovirt-users] 4.0 x 4.1

Yedidyah Bar David didi at redhat.com
Tue Jan 24 20:51:51 UTC 2017


On Tue, Jan 24, 2017 at 7:37 PM, Pavel Gashev <Pax at acronis.com> wrote:
> Karli,
>
> You’re right. Actually, when I did encounter the bugs in 4.0.5, all of them had been already found and fixed.

Actually, you can do that proactively - if you consider upgrading to
some version, you can search bugzilla for bugs targetted to the next
one, and if any of them look serious, wait.

> No doubt that developers do their hard job well. Unfortunately, due to the holydays there was a two-month gap between releases. 4.0.6-pre had another issue. I personally had to build my own hot-fix oVirt release with all the fixes and without changes under development. I can only guess what other users experienced.

See my earlier reply in this thread about the risks you take by doing that.

That said, if that's what you want, you can also use the 4.0 nightly snapshot:

https://www.ovirt.org/develop/dev-process/install-nightly-snapshot/

Was using this significantly different than what you built yourself?

Best,

>
> -----Original Message-----
> From: Karli Sjöberg <karli.sjoberg at slu.se>
> Reply-To: Karli Sjöberg <karli.sjoberg at slu.se>
> Date: Tuesday 24 January 2017 at 15:24
> To: "fernando.frediani at upx.com.br" <fernando.frediani at upx.com.br>, Pavel Gashev <Pax at acronis.com>, "users at ovirt.org" <users at ovirt.org>
> Subject: Re: [ovirt-users] 4.0 x 4.1
>
> On Tue, 2017-01-24 at 11:06 +0000, Pavel Gashev wrote:
>> I'd like to apologize for 'ugly' word. From my own personal
>> experience 4.0.5 had some bugs which spoiled my impression from 4.0.
>> Fortunately most of them are fixed in 4.0.6.
>
> I should really not throwing stone in glass houses here, since we´re
> still running 3.6 (I know, I know), but...
>
> If everyone thought like that, no one would have tested and gotten
> those bugs fixed in 4.0.6 either, see what I´m saying?
>
> So if people hadn´t tested and bug-reported those things, your
> impression of 4.0.6 would probably have been just as bad.
>
> Just my two cents.
>
> /K
>
>>
>> -----Original Message-----
>> From: <users-bounces at ovirt.org> on behalf of Pavel Gashev <Pax at acroni
>> s.com>
>> Date: Tuesday 24 January 2017 at 13:38
>> To: Fernando Frediani <fernando.frediani at upx.com.br>, "users at ovirt.or
>> g" <users at ovirt.org>
>> Subject: Re: [ovirt-users] 4.0 x 4.1
>>
>> I started with oVirt 3.6. It became stable since 3.6.7 just when 4.0
>> is released. Also I use 4.0. The previous 4.0.5 was ugly, 4.0.6 can
>> be considered more or less stable, and 4.1 is going to be released
>> soon. Thus, I’d start with 4.0 and upgrade to 4.1 when 4.2 is
>> released.
>>
>> -----Original Message-----
>> From: <users-bounces at ovirt.org> on behalf of Fernando Frediani <ferna
>> ndo.frediani at upx.com.br>
>> Date: Monday 23 January 2017 at 22:36
>> To: "users at ovirt.org" <users at ovirt.org>
>> Subject: [ovirt-users] 4.0 x 4.1
>>
>> I am deploying a oVirt environment which will not get production
>> data
>> immediately.
>>
>> Obviously I would rather use 4.1 RC due the many changes and fixes
>> present. Later when 4.1 becomes stable then upgrade to it.
>> Does anyone see any problem in doing that way or would it be more
>> advisable to start with 4.0.6 and upgrade to 4.1 stable when time
>> comes ?
>>
>> My concern are the issue people related they had when upgrading from
>> one
>> major version to another in the past.
>>
>> Thanks
>>
>> Fernando
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi


More information about the Users mailing list