Hi All, Agenda for this week meeting: - Implementation of bridged networks - Clone Vm from snapshot - Automatic recovery of entities Thanks, Livnat _______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

----- Original Message ----- > From: "Yaniv Kaul" <ykaul(a)redhat.com&gt; > To: "Livnat Peer" <lpeer(a)redhat.com&gt; > Cc: engine-devel(a)ovirt.org > Sent: Wednesday, February 15, 2012 1:35:56 PM > Subject: Re: [Engine-devel] agenda for today's meeting > > On 02/15/2012 01:21 PM, Livnat Peer wrote: >> Hi All, >> Agenda for this week meeting: >> >> - Implementation of bridged networks >> - Clone Vm from snapshot >> - Automatic recovery of entities >> >> Thanks, Livnat >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel > > If there's time, I'd be happy to add another topic to the agenda: > - upstream stabilization (especially considering the recent failures > in > unit tests) > Y. +1.

> _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel >

Since regretfully there was no time for my topic, I'll convey it via email. I'd like to suggest 3 simple rules to assist in keeping the projects stable: 1. If you've broken the Jenkins automated tests, provide a fix ASAP. 2. Don't fix what's ain't broken. 3. Follow rules 1 & 2 at all times. Thanks, Y.

On 02/15/2012 03:51 PM, Livnat Peer wrote: > On 15/02/12 13:39, Eyal Edri wrote: >> >> ----- Original Message ----- >>> From: "Yaniv Kaul&quot;&lt;ykaul(a)redhat.com&gt; >>> To: "Livnat Peer&quot;&lt;lpeer(a)redhat.com&gt; >>> Cc: engine-devel(a)ovirt.org >>> Sent: Wednesday, February 15, 2012 1:35:56 PM >>> Subject: Re: [Engine-devel] agenda for today's meeting >>> >>> On 02/15/2012 01:21 PM, Livnat Peer wrote: >>>> Hi All, >>>> Agenda for this week meeting: >>>> >>>> - Implementation of bridged networks >>>> - Clone Vm from snapshot >>>> - Automatic recovery of entities >>>> >>>> Thanks, Livnat >>>> _______________________________________________ >>>> Engine-devel mailing list >>>> Engine-devel(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>> If there's time, I'd be happy to add another topic to the agenda: >>> - upstream stabilization (especially considering the recent failures >>> in >>> unit tests) >>> Y. >> +1. >> > This was added to agenda. > >>> _______________________________________________ >>> 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

On Wed, Feb 15, 2012 at 11:15:27AM -0500, Jon Choate wrote: > I'd like to add to that: > > If you give at patch the verified flag this implies that you have: > 1. pulled the patch locally and ensured that it builds > 2. have run all the unit tests and ensure that they all pass > > If either of these are not true, you need to give the patch "-1 > Fails" If you don't do this you are as much to blame as the author. There's a jenkins plugin that builds each patch and gives -1 or +1 depending on if it builds. Now I don't know if we have the computing power to do the same, but it might be worth considering. See https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.