Martina,
per the discussion and since no comments on suggestion, I've created a
new project on gerrit called ovirt-engine-sdk-tests.
configuration includes: fast forward, change-id and signed-off-by required.
I'll define you as maintainer for it once you register to gerrit.
please update the website to reflect that sub repo under:
http://www.ovirt.org/project/subprojects/
Thanks,
Itamar
On 04/19/2012 04:02 PM, Mike Burns wrote:
On Thu, 2012-04-19 at 15:41 +0300, Itamar Heim wrote:
On 04/19/2012 03:27 PM, Mike Burns wrote:
On Thu, 2012-04-19 at 14:35 +0300, Itamar Heim wrote:
On 04/19/2012 02:18 PM, Martina Kollarova wrote:
Hello,
I created a set of tests for the ovirt-engine-sdk that could be run
using jenkins on each commit. Could you please create a git (+ gerrit)
repo for this?
I'm not sure this merits an 'incubation' project, and I'm fine with
creating a separate repo for this as a sub project of the sdk and
defining you as a maintainer for it.
but looking for comments from others on the mailing list before doing this.
I'm ok with the new repo, but couldn't it be included as a directory of
the ovirt-engine-sdk project? If that doesn't make sense in this case,
then it's fine.
from past experience, when a testing repo is used for system test (not
unitests), you want to be able to track changes in tests vs. changes in
code (and this repo would test some of the engine/vdsm as well).
this doesn't lend to branches too well.
hence i'm for a separate repo.
Ok, just needed to ask the question.
ACK from me.
Mike
Agree that no incubation would be needed.
Mike
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra