Open Stack

On 03/27/2015 06:57 AM, Pavlo Shchelokovskyy wrote:
> Hi,
> 
> On Thu, Mar 26, 2015 at 10:26 PM, Zane Bitter <zbitter at redhat.com
> <mailto:zbitter at redhat.com>> wrote:
> 
>> [snip]
>> 
>>>         3) move the integration tests to a separate repo and use it as git
>>>         submodule in the main tree. The main reasons not to do it as far
>>>         as I've
>>>         collected are not being able to provide code change and test in
>>>         the same
>>>         (or dependent) commits, and lesser reviewers' attention to a
>>>         separate repo.
>> 
> 
>>     -0
>> 
>>     I'm not sure what the advantage is here, and there are a bunch of
>>     downsides (basically, I agree with Ryan). Unfortunately I missed the
>>     IRC discussion, can you elaborate on how decoupling to this degree
>>     might help us?
> 
> 
> Presumably this could enable a more streamlined packaging and publishing
> of the test suit (e.g. to PyPI). But I agree, right now it is not really
> needed given the downsides, I just brought it up as an extreme
> separation case to collect more opinions.
> 
> Given the feedback we have in the thread, I will proceed with the first
> point as this should have immediate benefit for the duration of the test
> job and already give help to those who want to package the test suit
> separately. Distutils stuff can be added later.
> 
> Best regards, 
> Pavlo Shchelokovskyy

If we only do 1 and 2, not 3 we get all the benefits (separate package,
streamlined publishing, etc) without having to deal with the submodule
disadvantages I (and you) mentioned earlier.

-- 
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.