[ovirt-users] [QE][ACTION NEEDED] oVirt 3.5.2 RC status - branching

[Sandro Bonazzola]

Hi,
We're going to start composing oVirt 3.5.2 RC on *2015-02-25 08:00 UTC* from 3.5 branch.
In order to stabilize the release a new branch ovirt-engine-3.5.2 will be created from the same git hash used for composing the RC.

Maintainers:
- Please be sure that 3.5 snapshot allow to create VMs before *2015-02-24 15:00 UTC*
- Please be sure that no pending patches are going to block the release before *2015-02-24 15:00 UTC*
- If any patch must block the RC release please raise the issue as soon as possible.

A release management entry has been added for tracking the schedule of 3.5.2 [0]

A bug tracker [1] has been created and currently has one open blocker.

Bug ID	Whiteboard	Status	Summary
1161012	infra	POST	task cleaning utility  should erase commands that have running tasks

Yair, can you please provide ETA for this?

There are still 46 bugs [2] targeted to 3.5.2.
Excluding node and documentation bugs we still have 37 bugs [3] targeted to 3.5.2.

Whiteboard	NEW	ASSIGNED	POST	Total
		0	1		0	1
docs		1	0		0	1
gluster		4	0		1	5
infra		2	2		3	7
integration	9	0		0	9
network		0	1		0	1
node		4	0		1	5
ppc		0	0		1	1
sla		4	0		0	4
storage		8	0		0	8
ux		1	0		0	1
virt		1	0		2	3
Total		34	4		8	46


Maintainers / Assignee:
- Please add the bugs to the tracker if you think that 3.5.2 should not be released without them fixed.
- Please update the target to 3.5.3 or later for bugs that won't be in 3.5.2:
  it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]

Community:
- If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5]


[0] http://www.ovirt.org/OVirt_3.5.z_Release_Management#oVirt_3.5.2
[1] http://bugzilla.redhat.com/1186161
[2] http://goo.gl/crVJPH
[3] http://goo.gl/2qTZZU
[4] http://www.ovirt.org/OVirt_3.5.2_Release_Notes
[5] http://www.ovirt.org/Testing/oVirt_3.5.2_Testing


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com