Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-26 Thread Federico Simoncelli
- Original Message - > From: "Sven Kieske" > To: users@ovirt.org > Sent: Thursday, October 23, 2014 6:42:11 PM > Subject: Re: [ovirt-users] [QE] oVirt 3.5.1 status > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > ple

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-23 Thread Sven Kieske
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, please consider: https://bugzilla.redhat.com/show_bug.cgi?id=1156115 as a backport to 3.5.1 I don't know if you plan to release a new vdsm version though and I also don't know if this patch is already matured enough, if I can test or help make th

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-23 Thread Sandro Bonazzola
Il 23/10/2014 15:07, Sven Kieske ha scritto: > > > On 23/10/14 08:49, Sandro Bonazzola wrote: >> Il 22/10/2014 13:51, Sven Kieske ha scritto: >>> On 22/10/14 13:12, Sven Kieske wrote: As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-23 Thread Sven Kieske
On 23/10/14 08:49, Sandro Bonazzola wrote: > Il 22/10/2014 13:51, Sven Kieske ha scritto: >> On 22/10/14 13:12, Sven Kieske wrote: >>> As it's a regression from 3.4 I'd sugest >>> https://bugzilla.redhat.com/show_bug.cgi?id=1145241 >>> as a blocker. >> >> To be a little more specific on this topi

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-22 Thread Sandro Bonazzola
Il 22/10/2014 13:51, Sven Kieske ha scritto: > On 22/10/14 13:12, Sven Kieske wrote: >> As it's a regression from 3.4 I'd sugest >> https://bugzilla.redhat.com/show_bug.cgi?id=1145241 >> as a blocker. > > To be a little more specific on this topic: > > This bug got introduced because of incomplet

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-22 Thread Sandro Bonazzola
Il 22/10/2014 13:12, Sven Kieske ha scritto: > > > On 22/10/14 08:32, Sandro Bonazzola wrote: >> Hi, >> now that oVirt 3.5.0 has been released is time to start planning for 3.5.1. >> >> Release management for 3.5.z has been created [1] >> Suggested schedule for 3.5.1, following the 1 month schedu

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-22 Thread Sven Kieske
On 22/10/14 13:12, Sven Kieske wrote: > As it's a regression from 3.4 I'd sugest > https://bugzilla.redhat.com/show_bug.cgi?id=1145241 > as a blocker. To be a little more specific on this topic: This bug got introduced because of incomplete release criteria: "MUST: Fully operational flow (define

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-22 Thread Gianluca Cecchi
On Wed, Oct 22, 2014 at 1:12 PM, Sven Kieske wrote: > > > On 22/10/14 08:32, Sandro Bonazzola wrote: > > Hi, > > now that oVirt 3.5.0 has been released is time to start planning for > 3.5.1. > > > > Release management for 3.5.z has been created [1] > > Suggested schedule for 3.5.1, following the

Re: [ovirt-users] [QE] oVirt 3.5.1 status

2014-10-22 Thread Sven Kieske
On 22/10/14 08:32, Sandro Bonazzola wrote: > Hi, > now that oVirt 3.5.0 has been released is time to start planning for 3.5.1. > > Release management for 3.5.z has been created [1] > Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, > are: > > General availability:

[ovirt-users] [QE] oVirt 3.5.1 status

2014-10-21 Thread Sandro Bonazzola
Hi, now that oVirt 3.5.0 has been released is time to start planning for 3.5.1. Release management for 3.5.z has been created [1] Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, are: General availability: 2014-12-02 RC Build: 2014-11-25 A tracker bug for 3.5.1 has