Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

----- Original Message ----- > From: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; > To: Users(a)ovirt.org, devel(a)ovirt.org > Sent: Wednesday, August 20, 2014 10:10:03 AM > Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status > > Hi, > early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 UTC*, > we'll discuss current status in today oVirt sync meeting and eventually > postpone RC2 by another week. > > Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*): > - Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20 > 15:00 UTC* > - Please be sure that no pending patches are going to block the release > before *2014-08-20 15:00 UTC* > - If any patch must block the RC release please raise the issue as soon as > possible. > > The bug tracker [1] shows the following proposed blockers to be reviewed: > > Whiteboard Bug ID Status Summary > infra 1127877 POST vdsm-tool configure --force does not configure qemu.conf > properly in the first run on a fresh install This isn't a blocker. Still working on that, but it shouldn't block anything.

> sla 1129261 NEW prepareImage api call fails with [Errno 2] No such file or > directory > sla 1130038 NEW prepareImage api call fails with [Errno 2] No such file or > directory > storage 1128776 POST Can't change a vm disk's storage domain from a file > domain to a block domain when creating a template from a vm > storage 1127294 POST Live Merge: Resolve unknown merge status in vdsm after > host crash > storage 1109920 POST Live Merge: Extend internal block volumes during merge > > > And the following dependencies still open: > Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images > opened for writing > Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block > storage > > > Some of above blockers may be dropped on today oVirt sync meeting if still > open. > Some of the bugs blocking the release prevents automated testing to verify > the release. > Please fix them as soon as possible. > > > Feature freeze is now effective, and branch has been created. > All new patches must be backported to 3.5 branch too. > Features completed are marked in green on Features Status Table [2] > > There are still 425 bugs [3] targeted to 3.5.0. > Excluding node and documentation bugs we still have 381 bugs [4] targeted to > 3.5.0. > > More in detail [5]: > > Whiteboard NEW ASSIGNED POST Total > <unassigned> 7 . . 7 > gluster 9 5 2 16 > i18n . . 1 1 > infra 28 2 7 37 > integration 25 . 6 31 > network 18 1 15 34 > node 24 6 6 36 > ppc 2 . 4 6 > sla 38 . 18 56 > storage 86 10 9 105 > ux 22 2 . 24 > virt 59 4 9 72 > Total 318 30 77 425 > > > Maintainers / Assignee: > - Please ensure that completed features are marked in green on Features > Status Table [2] > - Please remember to rebuild your packages before *2014-08-20 15:00* > (supposing we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise nightly > snapshot will be taken. > - If you find a blocker bug please remember to add it to the tracker [1] > - Please fill release notes, the page has been created here [6] > - Please review and add test cases to oVirt 3.5 Third Test Day [7] > - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0: > it will ease gathering the blocking bugs for next releases. > > > Community: > - Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th. > - You're welcome to join us testing next beta release and getting involved in > oVirt Quality Assurance[8] > > > [1] http://bugzilla.redhat.com/1073943 > [2] http://bit.ly/17qBn6F > [3] http://red.ht/1pVEk7H > [4] http://red.ht/1zT2mSq > [5] http://red.ht/1q7SqNL > [6] http://www.ovirt.org/OVirt_3.5_Release_Notes > [7] http://www.ovirt.org/OVirt_3.5_TestDay > [8] http://www.ovirt.org/OVirt_Quality_Assurance > > Thanks, > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >