----- Original Message -----
From: "Moti Asayag" <masayag@redhat.com> To: "Lior Vernia" <lvernia@redhat.com> Cc: "Kobi Ianko" <kobi@redhat.com>, devel@ovirt.org Sent: Monday, June 23, 2014 11:31:33 PM Subject: Re: [ovirt-devel] Testing backported changes
----- Original Message -----
From: "Lior Vernia" <lvernia@redhat.com> To: "Kobi Ianko" <kobi@redhat.com> Cc: devel@ovirt.org Sent: Monday, June 23, 2014 5:10:04 PM Subject: Re: [ovirt-devel] Testing backported changes
I use a different DB for each version I'm backporting to, highly recommended. The only (moderate) pain is to reinstall hosts when moving between versions (assuming you're using the same hosts).
+1
In addition, you can use a vm as a host for 3.4 (fakeqemu/nested) instead re-installing the host.
Moti, That's a great idea! I would like to add that you might also find the need to have different maven repositories for different versions. You can have it nicely down (IMHO ) with alternatives + symlinks or just symlinks + some script.
On 23/06/14 16:47, Kobi Ianko wrote:
Hi, Is there a nice way to check changes I backported to 3.4.1 without messing my 3.5 DB?
10x _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel