Re: [Engine-devel] Time to move to 3.3.0-SNAPSHOT?
On 01/21/2013 10:28 AM, Omer Frenkel wrote:
----- Original Message -----
> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> To: "Michael Pasternak" <mpastern(a)redhat.com>
> Cc: "Juan Hernandez" <jhernand(a)redhat.com>, engine-devel(a)ovirt.org
> Sent: Monday, January 21, 2013 8:27:36 AM
> Subject: Re: [Engine-devel] Time to move to 3.3.0-SNAPSHOT?
>
>
>
> ----- Original Message -----
>> From: "Michael Pasternak" <mpastern(a)redhat.com>
>> To: "Juan Hernandez" <jhernand(a)redhat.com>
>> Cc: engine-devel(a)ovirt.org
>> Sent: Sunday, January 20, 2013 3:24:58 PM
>> Subject: Re: [Engine-devel] Time to move to 3.3.0-SNAPSHOT?
>>
>> On 01/17/2013 01:04 PM, Juan Hernandez wrote:
>>> Once 3.2.0 is released I think we should move to 3.3.0-SNAPSHOT
>>> in
>>> the master branch:
>>
>> +1
> I agree, and this is not the only place where should start marking
and cluster compatibility version..
all above is true, but Juan meant preparing MVN infra for the next
development iteration, while you're talking about engine internals,
maybe we should file BZs on that (as next version tasks) or should we
define new process of preparing for the next version that will include both?
> "3.3.0" - what about upgrade scripts?
>
>>
>>>
>>> http://gerrit.ovirt.org/11143
>>
>>
>> --
>>
>> Michael Pasternak
>> RedHat, ENG-Virtualization R&D
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
--
Michael Pasternak
RedHat, ENG-Virtualization R&D