<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jorick Astrego" <j.astrego@netbulae.eu><br><b>To: </b>users@ovirt.org<br><b>Sent: </b>Tuesday, March 18, 2014 12:33:30 PM<br><b>Subject: </b>Re: [Users] oVirt 3.5 planning<br><div><br></div>
Hi,<br><br>
When I used VMWare workstation many years ago, one of the features I couldn't live without was the layered snapshots. When testing it was extremely productive to have multiple branches of snapshots of the VM and I could revert to any point.</blockquote><div><br></div><div>I agree. The "snapshots" should be a tree and not a stack. When you "review" a snapshot, you should be able to choose, in addition to 'commit' (forget all the newer ones) and 'undo', also something like 'branch' (just keep everything).</div><div><br></div><div>Note that this is partially possible today by cloning a snapshot (to a VM) but imo is much less comfortable.</div><div><span style="font-size: 12pt;">-- </span></div><div><span name="x"></span>Didi<br><span name="x"></span><br></div></div></body></html>