Open Stack

On Mon, Sep 05, 2016 at 02:46:11PM +1000, Matthew Oliver wrote:
> Thanks Tony,
> 
> Yup that's my understanding too.
> 
> Like you said, thanks to the upper-constraints having the correct version
> (4.7.0), and the fact that currently the swiftclient has oslosphinx
> unconstrained, means that the online documentation builds OK and the docs
> job passes in the gate. Further, anyone trying to build the
> python-swiftclient documentation from a fresh install will also be fine, as
> pip should download the latest.
> 
> We definitely don't want to rock the boat while everyone is trying to
> stabilise for the next release, so I think option 2 or 3 are two good
> solutions. Personally, because of upper constraints and the fact that there
> is a rather simple (or 2 [upgrade or comment out a line]) work arounds, I'm
> personally leading for option 2. Rather then adding something hacky that
> will be removed in month or so.

Just a small clarification.  Any patch you add similar to option 3 will need to
be in place on the newton branch for it's lifetime.  Anything on master will as
you say be removable after a month or so.

> I'm also happy to go with option 2 and volunteer to raise option 3 as a
> patch if it does turn out to be a major problem or others.

Thanks Matt!

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160905/dbd02071/attachment.pgp>