Re: [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status

2014-05-28 Thread Sandro Bonazzola
Il 28/05/2014 16:15, Gilad Chaplik ha scritto: > - Original Message - >> From: "Sandro Bonazzola" >> To: "users" , devel@ovirt.org >> Sent: Wednesday, May 28, 2014 10:13:06 AM >> Subject: [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status >> >> Hi, >> We're preparing for fea

Re: [ovirt-devel] 3.5 Time-frame: pushing feature freeze

2014-05-28 Thread Sandro Bonazzola
Il 28/05/2014 17:01, Doron Fediuck ha scritto: > Hi, > The current date for feature freeze is May 30. > Based on today's weekly sync[1], it seems that most teams require > additional 2 weeks to conclude current work. > > Therefore I suggest to set an updated FF milestone for June 15. +1 Will all

Re: [ovirt-devel] discussion: URI format for libvirt metadata

2014-05-28 Thread Doron Fediuck
- Original Message - > From: "Dan Kenigsberg" > To: "Kobi Ianko" > Cc: "Doron Fediuck" , devel@ovirt.org > Sent: Wednesday, May 28, 2014 4:55:33 PM > Subject: Re: [ovirt-devel] discussion: URI format for libvirt metadata > > On Wed, May 28, 2014 at 08:58:33AM -0400, Kobi Ianko wrote: >

[ovirt-devel] 3.5 Time-frame: pushing feature freeze

2014-05-28 Thread Doron Fediuck
Hi, The current date for feature freeze is May 30. Based on today's weekly sync[1], it seems that most teams require additional 2 weeks to conclude current work. Therefore I suggest to set an updated FF milestone for June 15. If you need more time or think we should not change the current date pl

Re: [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status

2014-05-28 Thread Gilad Chaplik
- Original Message - > From: "Sandro Bonazzola" > To: "users" , devel@ovirt.org > Sent: Wednesday, May 28, 2014 10:13:06 AM > Subject: [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status > > Hi, > We're preparing for feature freeze scheduled for 2014-05-30. > We're going to

Re: [ovirt-devel] Python-GTK User Portal

2014-05-28 Thread Amador Pahim
On Tue, May 27, 2014 at 7:48 AM, Vojtech Szocs wrote: > Hi, this project looks nice! > > Indeed, UserPortal can be sluggish on devices with limited performance. > Going for custom, light-weight UserPortal sounds like a natural choice, > "samples-portals" repo sounds like a natural place :) The co

Re: [ovirt-devel] discussion: URI format for libvirt metadata

2014-05-28 Thread Dan Kenigsberg
On Wed, May 28, 2014 at 08:58:33AM -0400, Kobi Ianko wrote: > > > - Original Message - > > From: "Doron Fediuck" > > To: "Kobi Ianko" > > Cc: devel@ovirt.org > > Sent: Wednesday, May 28, 2014 3:06:44 PM > > Subject: Re: [ovirt-devel] discussion: URI format for libvirt metadata > > > >

Re: [ovirt-devel] discussion: URI format for libvirt metadata

2014-05-28 Thread Kobi Ianko
- Original Message - > From: "Doron Fediuck" > To: "Kobi Ianko" > Cc: devel@ovirt.org > Sent: Wednesday, May 28, 2014 3:06:44 PM > Subject: Re: [ovirt-devel] discussion: URI format for libvirt metadata > > for the sake of future updates, I suggest we use > current suggestion with a ver

Re: [ovirt-devel] discussion: URI format for libvirt metadata

2014-05-28 Thread Doron Fediuck
for the sake of future updates, I suggest we use current suggestion with a version in the URI. ie- http://ovirt.org/vm/tune/1.0 Or even- http://ovirt.org/1.0/vm/tune - Original Message - > From: "Kobi Ianko" > To: devel@ovirt.org > Cc: "Dan Kenigsberg" , "Doron Fediuck" > > Sent: Wedn

Re: [ovirt-devel] discussion: URI format for libvirt metadata

2014-05-28 Thread Kobi Ianko
The URL that we will go with is "http://ovirt.org/vm/tune";. The address is self explainable, it will contain vm tunable parameters and refer to a web page explaining the parameters. 10x. > > - Forwarded Message - > > > From: "Dan Kenigsberg" > > > To: "Kobi Ianko" > > > Cc: devel@ovi

Re: [ovirt-devel] oVirt 3.4.2 branching

2014-05-28 Thread Sandro Bonazzola
Il 27/05/2014 15:09, Sandro Bonazzola ha scritto: > Hi, > we're going to create ovirt-engine-3.4.2 branch tomorrow morning 08:00 UTC in > order to allow 3.4.3 development starting on 3.4 branch while we prepare > for 3.4.2 GA release. > So starting tomorrow morning, if you have patches targeted to

[ovirt-devel] [QE][ACTION NEEDED] oVirt 3.4.2 status

2014-05-28 Thread Sandro Bonazzola
Hi, We're going to start composing oVirt 3.4.2 GA on *2014-06-10 08:00 UTC* from 3.4.2 branches. The bug tracker [1] shows no blocking bugs for the release There are still 58 bugs [2] targeted to 3.4.2. Excluding node and documentation bugs we still have 27 bugs [3] targeted to 3.4.2. Maintain

[ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status

2014-05-28 Thread Sandro Bonazzola
Hi, We're preparing for feature freeze scheduled for 2014-05-30. We're going to compose a Second Alpha on Firday *2014-05-30 08:00 UTC*. Maintainers: - Please be sure that master snapshot allow to create VMs before *2014-05-29 15:00 UTC* The bug tracker [1] shows the following proposed blockers