[ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
Oved Ourfali
ovedo at redhat.com
Wed Sep 17 13:09:04 UTC 2014
----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: devel at ovirt.org, Users at ovirt.org
> Sent: Wednesday, September 17, 2014 2:46:10 PM
> Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
>
> Hi,
> We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day
> results and oVirt Sync Meeting decisions) on Monday 2014-09-22.
>
> Maintainers:
> - Please be sure that 3.5 snapshot satisfy release criteria[9]
> - Please be sure that no pending patches are going to block the release
> - If any patch must block the GA release please raise the issue as soon as
> possible.
> - If any packages need a rebase please raise the issue as soon as possible.
> - Be aware that packages that doesn't need a rebase must be re-built with
> final release versioning from the RC2 tag.
>
> The bug tracker [1] shows the following proposed blockers to be reviewed:
>
> Bug ID Whiteboard Status Summary
> 1142256 integration POST engine-setup does not write conf file to allow
> accessing reports
>
> 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
>
> The following bugs are keyworded as Regression and not marked as blockers[10]
>
> Bug ID Whiteboard Status Summary
> 1135909 infra POST [Event log] Wrong warning about available swap memory of
> host [1023MB], when actually host has [1024MB] memory size
We're still discussing whether to address that on engine/VDSM side.
Doesn't seem urgent, though, so I wouldn't consider that as a blocker.
We didn't see any change with regards to that, so I'm surprised it is a Regression at all...
> 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1
> fails with InquireNotSupportedError
> 1110444 ux POST bookmark selection does not work on first try
> 1138314 virt NEW Fail to start vm with payload.
>
> 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 83 bugs [3] targeted to 3.5.0.
> Excluding node and documentation bugs we still have 58 bugs [4] targeted to
> 3.5.0.
>
> More in detail [5]:
>
> Whiteboard NEW ASSIGNED POST Total
> docs 14 1 0 15
> gluster 9 4 2 15
> i18n 0 0 1 1
> integration 1 1 1 3
> node 6 4 0 10
> ppc 2 0 4 6
> sla 5 0 8 13
> storage 0 0 3 3
> virt 12 0 5 17
> Total 49 10 24 83
>
>
> Maintainers / Assignee:
> - Please ensure that completed features are marked in green on Features
> Status Table [2]
> - 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 results from 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:
> - You're welcome to join us testing next release candidate and getting
> involved in oVirt Quality Assurance[8]
>
>
> [1] http://bugzilla.redhat.com/1073943
> [2] http://goo.gl/4SuYdE
> [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://etherpad.ovirt.org/p/3.5-testday-3
> [8] http://www.ovirt.org/OVirt_Quality_Assurance
> [9]
> http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
> [10] http://goo.gl/uavikG
>
> Thanks,
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
More information about the Users
mailing list