oVirt refers to "virtual machine disks". This terminology, however, is inaccurate - a disk can belong to a template, or be completely detached (floating).
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Setting as 'StudentProject', in the hope that all changes are indeed UI only.
I'm not sure how to verify since we have many places where the "virtual (machine) disk" terminology is used. Idan, what do you suggest?
The idea is to distinguish between a general virtual disk (that can be a vm disk or even a template or floating disk) and a vm disk. In case that the disk must belong to a vm, it's ok to call it a vm disk. In case that it doesn't necessarily belong to a vm, it should be called virtual disk.
Following a f2f conversation with Idan and Tal Nisan, they suggested to test that the terminology is changed in UI for the basic flows (disk creation, deletion, move etc.)
Tested basic disk operations with floating disks, attached to VM disks and attached to template disk. The terminology used in each is correct, for example, for a disk attached to VM, the following event log is shown when extending it: " Size of the disk 'test1_Disk1' was successfully updated to 2 GB by admin@internal. " Another example, of removal of a disk attached to template: " VM test1 powered off by admin@internal (Host: blond-vdsh) (Reason: No reason was returned for this operation failure. See logs for further details.). " Verified using: ovirt-engine-4.0.0-0.0.master.20160406161747.gita4ecba2.el7.centos.noarch
oVirt 4.0.0 has been released, closing current release.