On 2014-10-22 12:31:53 -0400 (-0400), Davanum Srinivas wrote:
> fyi, latest update after discussion on #openstack-infra, consensus
> seems to be to allow projects to add to g-r.
[...]
If that's deemed unacceptable for other reasons, the alternative
solution which was floated is to tweak setup_pack
fyi, latest update after discussion on #openstack-infra, consensus
seems to be to allow projects to add to g-r.
131+ All OpenStack projects, regardless of status, may add entries to
132+ ``global-requirements.txt`` for dependencies if the project is going
133+ to run integration tests under a devs
Dear requirements-core folks,
Here's the review as promised:
https://review.openstack.org/130210
Thanks,
dims
On Wed, Oct 22, 2014 at 7:27 AM, Davanum Srinivas wrote:
> Matt,
>
> I've submitted a review to remove the gate-nova-docker-requirements
> from nova-docker:
>
> https://review.openstack
Matt,
I've submitted a review to remove the gate-nova-docker-requirements
from nova-docker:
https://review.openstack.org/#/c/130192/
I am good with treating the current situation with DSVM jobs as we
"bug" if there is consensus. I'll try to dig in, but we may need Dean,
Sean etc to help figure i
On Tue, Oct 21, 2014 at 08:09:38PM -0400, Davanum Srinivas wrote:
> Hi all,
>
> On the cross project meeting today, i promised to bring this to the
> ML[1]. So here it is:
>
> Question : Can a StackForge project (like nova-docker), depend on a
> library (docker-py) that is not specified in global
Hi all,
On the cross project meeting today, i promised to bring this to the
ML[1]. So here it is:
Question : Can a StackForge project (like nova-docker), depend on a
library (docker-py) that is not specified in global requirements?
Right now the answer seems to be "No", as enforced by the CI sys
