Il 27/02/2014 14:42, Ademar Reis ha scritto:
I believe we're all in sync here with the goals. What we're not
in sync is how to implement it in practice (and I don't see
anything in the message from Paolo that makes me believe he wants
the old next concept back).
As 5% developer, 95% "power user" of virt-test, all I want is a master
branch that I can use for both of these tasks:
a) developing simple patches and bugfixes
b) running a few simple test matrices. Most of the time, all I do is
just a sequence of 16 unattended installs with "./run -c install.cfg -t
qemu". Yet it breaks all the time!
I only update when I have a particularly pressing itch that requires me
to cook a patch, or when I have to test some new guest that has just
been added. Roughly it's every 2-3 months. All I know is that when
"next" existed, using master just worked, while right now I cannot even
use stable releases because they're just as unstable as master. This is
what made me worry about declining quality of releases.
I don't care much about how the integration branch is done. Whether
it's done by automatic scripts or by the maintainer doing "push -f"
repeatedly is a detail that I would not be exposed to. It's quite
possible that Lucas was not doing it in a very orthodox way, and that it
was time consuming. However, the lack of an integration branch IMHO can
be perceived in day-to-day development and usage of autotest.
Paolo
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
