----- Original Message -----
From: "Moran Goldboim" <mgoldboi(a)redhat.com>
To: "engine-devel" <engine-devel(a)ovirt.org>, vdsm-devel(a)ovirt.org,
users(a)ovirt.org
Sent: Tuesday, July 30, 2013 6:05:46 PM
Subject: [Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers
review]
We would like to go a head on oVirt 3.3 release process and issue an RC
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
Please use proper notation...
ovirt-engine-3.3.0 branch for 3.3.0 release cycle
ovirt-engine-3.3.0_rc1 - for rc1 tag or branch
...
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 - Tracker: oVirt 3.3 release
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel