Open Stack

hi,

On Sat, Oct 24, 2015 at 9:25 PM, Doug Wiegley
<dougwig at parksidesoftware.com> wrote:
>
>> On Oct 19, 2015, at 5:33 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>
>>> On 16 Oct 2015, at 10:50, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>>>
>>> if i move fwaas tests from neutron to neutron-fwaas, [1]
>>> is there easy way to run them together with the rest of neutron api tests
>>> for gate-neutron-dsvm-api job?
>>
>> Before we jump in to reflect current gating status-quo, do we have a definite answer why we want to keep the gate coupling in place? Can’t we leave the fwaas api job for fwaas repo only? Do we think core is unstable enough to justify additional coupling? Is core bad at handling backwards compatibility when it comes to (re)moving code that is unneeded for the core repo?
>
> Core is absolutely dreadful at backwards compatibility (I’m talking recent history here.) The co-gate is necessary to guard against that at the moment.

do you still want to keep the co-gate?
i was trying to keep the co-gate [2] but armando doesn't seem to like it.
any suggestions?

[2] https://review.openstack.org/#/c/242925/

>
> Thanks,
> doug
>
>>
>> That may actually be a dumb question, so don’t hesitate to point out obvious reasons to keep co-gating.
>>
>> Ihar
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev