Re: [ACTION REQUIRED] stabilization branches for 4.1
Hi,
maybe I've not made myself clear enough about stabilization branching, but
it should have happened yesterday as deadline.
I may understand that projects which are not under heavy development like
otopi or optimizer or external scheduler will keep master until they really
start looking iinto 4.2 but I would expect projects like vdsm branching and
enter bugfix only mode.
Still, I don't see ovirt-4.1 branch there and patches being merged without
bug-url pointing to 4.1 bugs.
Can we please stabilize vdsm? We have scheduled beta2 tomorrow morning at
11:00 TLV time.
On Mon, Dec 19, 2016 at 10:00 AM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
ovirt-engine 4.1 branch has been created.
On Mon, Dec 19, 2016 at 8:56 AM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
> A gentle reminder branching will happen in 1 hour
>
> On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo(a)redhat.com>
> wrote:
>
>> In order to stabilize the build and allow to prepare jenkins on time, 4.1
>> branches need to be created before or on Monday Dec 19th.
>>
>> oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time
>> (10:00 AM CET).
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
Attachments:
- attachment.html (text/html — 4.2 KB)