The short answer is: "you can test and develop it locally but you cannot push 
it upstream until you get the dependencies released." As much as that may be 
frustrating, it prevents an enormous amount of pain which OpenStack has gone 
through in the past when things fail to be released as expected.

 Please work with the Neutron team to get their end of things done first.

Thanks!

    - Gabriel

> -----Original Message-----
> From: Monty Taylor [mailto:[email protected]]
> Sent: Wednesday, July 31, 2013 10:29 PM
> To: [email protected]
> Subject: Re: [openstack-dev] [Horizon] how to add unmerged dependency
> to test-requirements
> 
> Hi!
> 
> Not really. We don't support OpenStack projects having dependencies on
> unreleased software. What does fwaas come from? Is this part of neutron?
> 
> On 08/01/2013 01:24 AM, Kuang-Ching Wang wrote:
> > Hi, I am working on fwaas Horizon support, which requires fwaas CLI to
> work.  Since fwaas CLI has not been merged (though it is functional), is there
> anyway I can specify the dependency in horizon/test-requirements file, such
> that Jenkins would be able to run for my horizon patch.
> >
> > Thanks!
> > KC
> > _______________________________________________
> > OpenStack-dev mailing list
> > [email protected]
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> _______________________________________________
> OpenStack-dev mailing list
> [email protected]
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to