[Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review]

[Dan Kenigsberg]

On Tue, Jul 30, 2013 at 06:05:46PM +0300, Moran Goldboim wrote:
> 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
>     ...
> 
> 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

I've just tagged vdsm-4.12.0 and branched ovirt-3.3 branch for the vdsm
repository starting at git has 620343d6317c849fc985a5083cebb68c995f7c15.

Expect a deluge of non-ovirt-3.3 merges to the master branch soon.
Future ovirt-3.3 fixes would have to be backported and cherry-picked.

Dan.