Hi Soren,
yeah I've seen your old youtube video on what is new in virtualization for 
Ubuntu since the name felt known :-).

The reason to not upload immediately is that I'd want to see if there are any 
other bad effects of attr being enabled that we might miss.
I'd want to see if e.g. migrations on disk images on shared storage run into 
trouble or something like that. To do so I'd run a bunch of regression tests in 
addition to what comes to my mind for this case in particular. Those tests need 
quite some time and allocation of systems - therefore they are most effective 
if coupled with a bunch of other big changes where the tests will cover "more 
new code".

In addition I'm away for quite some time in July, so if I break things
with an upload now I'm not around to clean up my mess.

And while the bug feels bad, it was open so long attracting only so few
people/reports that while it feels important for the two of us now it
might overall be not too urgent to squeeze it in asap.

I hope that explains why I have postponed the change to when I get to
merge a newer libvirt for groovy anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/691590

Title:
  libvirt restore exactly the old ownership of images

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/691590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to