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

The bug tracker [1] shows 1 open blocker:
Bug ID  Whiteboard      Status  Summary
1160846 sla             NEW     Can't add disk to VM without specifying disk 
profile when the storage domain has more than one disk profile

In order to stabilize the release a new branch ovirt-engine-3.5.1 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 *2014-12-08 15:00 
UTC*
- Please be sure that no pending patches are going to block the release before 
*2014-12-08 15:00 UTC*
- If any patch must block the RC release please raise the issue as soon as 
possible.
- Please provide an ETA for the pending blockers as soon as possible.

Infra:
- Please check Jenkins status for 3.5 jobs and sync with relevant maintainers 
if there are issues.

There are still 68 bugs [2] targeted to 3.5.1.
Excluding node and documentation bugs we still have 45 bugs [3] targeted to 
3.5.1.

Maintainers / Assignee:
- Please add the bugs to the tracker if you think that 3.5.1 should not be 
released without them fixed.
- Please update the target to 3.5.2 or later for bugs that won't be in 3.5.1:
  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]


[1] http://bugzilla.redhat.com/1155170
[2] http://goo.gl/7G0PDV
[3] http://goo.gl/6gUbVr
[4] http://www.ovirt.org/OVirt_3.5.1_Release_Notes
[5] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to