9:36 a.m.
Il 10/12/2014 16:54, Brian Proffitt ha scritto:
(On time this week!)
=========================
#ovirt: oVirt Weekly Sync
=========================
[cut]
* 3.5.z updates Two blockers have postponed RC again. New RC date
will
be discussed and decided in mailing list. (bkp, 15:30:01)
[cut]
Let's start the discussion and decision task.
We have an ETA on the last pending blocker for 3.5.1 on next week.
I suggest to postpone RC and GA after winter holidays.
What about:
RC - 2015-01-07
GA - 2015-01-14
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
11:45 a.m.
On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote:
Il 10/12/2014 16:54, Brian Proffitt ha scritto:
> (On time this week!)
>
> =========================
> #ovirt: oVirt Weekly Sync
> =========================
[cut]
> * 3.5.z updates Two blockers have postponed RC again. New RC date will
> be discussed and decided in mailing list. (bkp, 15:30:01)
[cut]
Let's start the discussion and decision task.
We have an ETA on the last pending blocker for 3.5.1 on next week.
I suggest to postpone RC and GA after winter holidays.
What about:
RC - 2015-01-07
GA - 2015-01-14
Can we have a vdsm respin before that? We get repeated reports of bugs
that are already solved in the stable branch.
4:22 p.m.
Il 11/12/2014 10:45, Dan Kenigsberg ha scritto:
On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote:
> Il 10/12/2014 16:54, Brian Proffitt ha scritto:
>> (On time this week!)
>>
>> =========================
>> #ovirt: oVirt Weekly Sync
>> =========================
>
> [cut]
>
>> * 3.5.z updates Two blockers have postponed RC again. New RC date will
>> be discussed and decided in mailing list. (bkp, 15:30:01)
>
> [cut]
>
> Let's start the discussion and decision task.
> We have an ETA on the last pending blocker for 3.5.1 on next week.
> I suggest to postpone RC and GA after winter holidays.
>
> What about:
> RC - 2015-01-07
> GA - 2015-01-14
Can we have a vdsm respin before that? We get repeated reports of bugs
that are already solved in the stable branch.
Can you elaborate on what's the request?
1) have a VDSM async release which should go in http://resources.ovirt.org/pub/ovirt-3.5/
as stable release
2) have a "beta" in http://resources.ovirt.org/pub/ovirt-3.5-pre taking latest
snapshot
If the request is 1, please provide the RPMs to be added to the stable repository.
If the request is 2, I can't see the added value from just enabling nightly 3.5
snapshot, run 'yum update "vdsm*"' and disable it.
I assume that not having replies to above dates other than this vdsm early release request
means all the other agree with the proposed date.
Updating the calendar accordingly.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
11:01 p.m.
On Fri, Dec 12, 2014 at 03:22:50PM +0100, Sandro Bonazzola wrote:
Il 11/12/2014 10:45, Dan Kenigsberg ha scritto:
> On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote:
>> Il 10/12/2014 16:54, Brian Proffitt ha scritto:
>>> (On time this week!)
>>>
>>> =========================
>>> #ovirt: oVirt Weekly Sync
>>> =========================
>>
>> [cut]
>>
>>> * 3.5.z updates Two blockers have postponed RC again. New RC date will
>>> be discussed and decided in mailing list. (bkp, 15:30:01)
>>
>> [cut]
>>
>> Let's start the discussion and decision task.
>> We have an ETA on the last pending blocker for 3.5.1 on next week.
>> I suggest to postpone RC and GA after winter holidays.
>>
>> What about:
>> RC - 2015-01-07
>> GA - 2015-01-14
>
> Can we have a vdsm respin before that? We get repeated reports of bugs
> that are already solved in the stable branch.
>
Can you elaborate on what's the request?
1) have a VDSM async release which should go in http://resources.ovirt.org/pub/ovirt-3.5/
as stable release
2) have a "beta" in http://resources.ovirt.org/pub/ovirt-3.5-pre taking latest
snapshot
If the request is 1, please provide the RPMs to be added to the stable repository.
It's 1. The stable branch vdsm is clearly better from the one shipped in
3.5.0.
I've tagged v4.16.9 for this occasion.
Yaniv, can you build an official ovirt build from this tag?
8:56 a.m.
Il 12/12/2014 22:01, Dan Kenigsberg ha scritto:
On Fri, Dec 12, 2014 at 03:22:50PM +0100, Sandro Bonazzola wrote:
> Il 11/12/2014 10:45, Dan Kenigsberg ha scritto:
>> On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote:
>>> Il 10/12/2014 16:54, Brian Proffitt ha scritto:
>>>> (On time this week!)
>>>>
>>>> =========================
>>>> #ovirt: oVirt Weekly Sync
>>>> =========================
>>>
>>> [cut]
>>>
>>>> * 3.5.z updates Two blockers have postponed RC again. New RC date will
>>>> be discussed and decided in mailing list. (bkp, 15:30:01)
>>>
>>> [cut]
>>>
>>> Let's start the discussion and decision task.
>>> We have an ETA on the last pending blocker for 3.5.1 on next week.
>>> I suggest to postpone RC and GA after winter holidays.
>>>
>>> What about:
>>> RC - 2015-01-07
>>> GA - 2015-01-14
>>
>> Can we have a vdsm respin before that? We get repeated reports of bugs
>> that are already solved in the stable branch.
>>
>
> Can you elaborate on what's the request?
> 1) have a VDSM async release which should go in
http://resources.ovirt.org/pub/ovirt-3.5/ as stable release
> 2) have a "beta" in http://resources.ovirt.org/pub/ovirt-3.5-pre taking
latest snapshot
>
> If the request is 1, please provide the RPMs to be added to the stable repository.
It's 1. The stable branch vdsm is clearly better from the one shipped in
3.5.0.
I've tagged v4.16.9 for this occasion.
Yaniv, can you build an official ovirt build from this tag?
Ok, let me know when we have the rpms.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
3626
days inactive
3630
days old
4 comments
2 participants
participants (2)
-
Dan Kenigsberg -
Sandro Bonazzola