Open Stack

On December 4, 2013 at 18:05:07, Jamie Lennox (jamielennox at redhat.com) wrote:


On Wed, 2013-12-04 at 20:48 -0500, David Stanek wrote: 
> On Wed, Dec 4, 2013 at 6:44 PM, Adrian Otto 
> <adrian.otto at rackspace.com> wrote: 
> Jamie, 
> 
> Thanks for the guidance here. I am checking to see if any of 
> our developers might take an interest in helping with the 
> upstream work. At the very least, it might be nice to have 
> some understanding of how much work there is to be done in 
> HTTPretty. 
> 
> 
> (Dolph correct me if I am wrong, but...) 
> 
> 
> I don't think that there is much work to be done beyond getting that 
> pull request merged upstream. Dolph ran the tests using the code from 
> the pull request somewhat successfully. The errors that we saw were 
> just in keystoneclient code. 

But I don't think that there own test suite runs under py33 with that 
branch. So they've hit the main issues, but we won't get a release in 
that state. 
Should we offer to bring HTTPretty under something like stackforge and leverage our CI infrastructure?  Not sure how open the owner/maintainers would be to this, but it would help to solve that issue… downside is that pull-requests are no longer (gerrit instead) used and IIRC CLA is still required for stackforge projects (might be a detractor).  Just a passing thought (that might be irrelevant depending on the owner/maintainer’s point of view).


—Morgan



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131204/69b1da25/attachment.html>