On 07/30/2013 06:05 PM, Moran Goldboim wrote:
We would like to go a head on oVirt 3.3 release process and issue an RC
how can we do this before folks review all the bugs with target release
of 3.3 and either suggest them as blockers or move them from 3.3?
there are currently 59 NEW, 7 ASSIGNED and 22 POST with target release
of 3.3?
http://alturl.com/aq23x
for tomorrow meeting:
Maintainers/ Package owners
==================
-branch your git repo (master) with 3.3 branch (making master ready for 3.4)
-for tomorrow meeting, overview [1], see if you have any changes to it
-if you don't have any blockers under your component, please branch 3.3
with RC1 branch
|
-master
|
-engine_3.3
|
-RC1
|
-engine_3.2
...
Users
====
with your experience from test day and with nightlies, if you feel there
are additional candidates to block this version for please add it to the
tracker bug [1].
Suggested Schedule
============
Wed Jul 31st - review of blockers for the version and component readiness
Mon Aug 5th - RC1 release
Wed Aug 7th - Release readiness review (in case of blockers an RC2 will
be issued)
Thanks.
[1]*Bug 918494* <https://bugzilla.redhat.com/show_bug.cgi?id=918494>
-Tracker: oVirt 3.3 release
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
