On 07/26/2013 06:51 AM, Lukáš Doktor wrote: > Dne 25.7.2013 21:52, Cleber Rosa napsal(a):> On 07/25/2013 04:41 PM, > Lucas Meneghel Rodrigues wrote: >> I do not see a single failure with your proposal. >> >> The only rule I'd add is that, once the library is added to Autotest, it >> should freeze on virt-test, so that we do not loose any >> fixes/improvements during that time. > > Well for some libraries which are under continuous development the > problem with newer versions vs. what is in current/stable/used framework > might be a problem. Eg. cgroup_utils. Currently it exists in booth > virt-test and autotest. To freeze it for one or two releases would be > really painful.
I think we already have some code for version-able classes no? Also, I think python's "future" mechanism is available to use also. I just don't understand the details, but I'm sure it's there. That would help in cases where some library is moved to autotest, but has some updates in virt-test. -- Chris Evich, RHCA, RHCE, RHCDS, RHCSS Quality Assurance Engineer e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214 _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
