----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Keith Robertson" <kroberts(a)redhat.com>
Cc: engine-devel(a)ovirt.org, arch(a)ovirt.org, "Eyal Edri"
<eedri(a)redhat.com>
Sent: Sunday, February 12, 2012 12:44:40 AM
Subject: Re: [Engine-devel] New oVirt GIT Repo Request
On 02/12/2012 12:41 AM, Itamar Heim wrote:
>> The Plan:
>> Step 1: Create naked GIT repos on
oVirt.org for the 3 tools.
>> Step 2: Link git repos to gerrit.
>
> above two are same step - create a project in gerrit.
> I'll do that if list doesn't have any objections by monday.
>
>> Step 3: Populate naked GIT repos with source and build standalone
>> spec
>> files for each.
>> Step 4: In one patch do both a) and b)...
>> a) Update oVirt manager GIT repo by removing tool source.
>> b) Update oVirt manager GIT repo such that spec has dependencies
>> on 3
>> new RPMs.
Also, run at list pylint jobs tracking changes to these new repos
(cc'd
eedri to coordinate with)
It shouldn't be a problem if we want to test python code (pyflakes/pylint) via gerrit
& jenkins.
(we might want to use -E just for errors, otherwise we'll get a lot of warnings we
can't handle).
testing java (+maven) code will require moving to maven 3.0.X due to jenkins plugins
backward compatible issues.
Eyal.