[ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.2 and 3.5.3 status

[Sandro Bonazzola]

Hi,

We have 1 open blocker for 3.5.2[1]:

Bug ID	Whiteboard	Status		Summary
1154399	network		ASSIGNED	VDSM script reset network configuration on every reboot when based on predefined bond


and 1 dependency not yet fixed:
Bug ID	Status	Whiteboard	Summary
1209486	POST	network		Networks created by vdsm are not persisted

ACTION: Assignee please provide an ETA for above bugs and check if they must block GA requiring another release candidate before GA.

We still have 1 bugs in MODIFIED and 3 on QA[2]:

 	MODIFIED	ON_QA	Total
network	0		1	1
sla	1		0	1
storage	0		1	1
virt	0		1	1
Total	1		3	4


ACTION: Testers: you're welcome to verify bugs currently ON_QA.
ACTION: Assingee and Maintainers to check modified bugs to see if they're fixed in RC4

All remaining bugs not marked as blockers have been moved to 3.5.3.
A release management entry has been added for tracking the schedule of 3.5.3[3]
A bug tracker [4] has been created for 3.5.3 and currently shows no blockers.

We have 26 bugs currently targeted to 3.5.3[5]:

Whiteboard	NEW	ASSIGNED	POST	Total
docs		1	0		0	1
external	1	0		0	1
gluster		1	0		0	1
infra		1	1		1	3
network		1	0		1	2
node		4	0		1	5
ppc		0	0		1	1
sla		4	0		0	4
storage		4	0		2	6
ux		1	0		0	1
virt		1	0		0	1
Total		19	1		6	26


ACTION: Maintainers / Assignee: to review the bugs targeted to 3.5.3 ensuring they're correctly targeted.
ACTION: Maintainers: to fill release notes for 3.5.2, the page has been created and updated here [6]
ACTION: Testers: please add yourself to the test page [7]


[1] https://bugzilla.redhat.com/1186161
[2] http://goo.gl/UEVTCf
[3] http://www.ovirt.org/OVirt_3.5.z_Release_Management#oVirt_3.5.3
[4] https://bugzilla.redhat.com/1198142
[5] https://bugzilla.redhat.com/buglist.cgi?quicksearch=product%3Aovirt%20target_release%3A3.5.3
[6] http://www.ovirt.org/OVirt_3.5.2_Release_Notes
[7] 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