From: "Antoni Segura Puimedon" <asegurap(a)redhat.com&gt; To: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; Cc: Users(a)ovirt.org, devel(a)ovirt.org Sent: Thursday, May 29, 2014 5:35:38 PM Subject: Re: [ovirt-users] [ovirt-devel] oVirt 3.5.0 release schedule updated ----- Original Message ----- > From: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; > To: Users(a)ovirt.org, devel(a)ovirt.org > Sent: Thursday, May 29, 2014 5:32:47 PM > Subject: [ovirt-devel] oVirt 3.5.0 release schedule updated > > Here is the updated schedule for oVirt 3.5.0. > These are tentative planning dates and may change: > > General availability: 2014-08-04 (Mon) > oVirt 3.5 Second Test Day: 2014-07-22 (Tue) > RC Build: 2014-07-16 (Wed) > oVirt 3.5 First Test Day: 2014-07-01 (Tue) > Branching - Beta release: 2014-06-26 (Thu) > Feature freeze: 2014-06-15 (Sun) > Second Alpha release: 2014-06-05 (Thu) Shouldn't the branching be at the feature freeze date and any change (bugfix) after that be first sent to master and then backported? I think it would really help stabilization and not to lower the speed of master for future changes.

> > Release management page has been updated accordingly: > http://www.ovirt.org/OVirt_3.5_release-management > > oVirt Google Calendar has been updated accordingly: > ICAL: > https://www.google.com/calendar/ical/ppqtk46u9cglj7l987ruo2l0f8%40group.c... > XML: > https://www.google.com/calendar/feeds/ppqtk46u9cglj7l987ruo2l0f8%40group.... > HTML: > https://www.google.com/calendar/embed?src=ppqtk46u9cglj7l987ruo2l0f8%40gr... > > > Thanks, > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users