15 Feb
2012
15 Feb
'12
9:26 a.m.
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"<ykaul@redhat.com> >>> To: "Livnat Peer"<lpeer@redhat.com> >>> Cc: engine-devel@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@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@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>>