Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Doug Hellmann
Excerpts from Anne Gentle's message of 2017-07-10 13:14:52 -0400: > On Mon, Jul 10, 2017 at 1:11 PM, Doug Hellmann wrote: > > Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > >> On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > >> > >> Of

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Anne Gentle
On Mon, Jul 10, 2017 at 1:11 PM, Doug Hellmann wrote: > Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: >> On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: >> > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just >> >

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Doug Hellmann
Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > > remove the feature at this point. However, this is going to necessitate some > >

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Anne Gentle
On Mon, Jul 10, 2017 at 12:20 PM, wrote: > On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: >> tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just >> remove the feature at this point. However, this is going to necessitate some >>

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread sfinucan
On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > remove the feature at this point. However, this is going to necessitate some > mechanical changes for most projects with docs and this mail serves as a >

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-08 Thread Jeremy Stanley
On 2017-07-07 18:03:11 -0500 (-0500), Monty Taylor wrote: > On 07/07/2017 12:12 PM, Jeremy Stanley wrote: [...] > > Better still, something like `tox -e venv -- sphinx-build` would > > be more in keeping with the spirit of the PTI to ensure projects > > don't encapsulate any secret sauce into a

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-07 Thread Monty Taylor
On 07/07/2017 12:12 PM, Jeremy Stanley wrote: On 2017-07-07 11:20:30 -0400 (-0400), Doug Hellmann wrote: [...] We also discussed changing the CI interface to build docs to use the "tox -e docs" command like contributors generally run locally. [...] Better still, something like `tox -e venv --

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-07 Thread Jeremy Stanley
On 2017-07-07 11:20:30 -0400 (-0400), Doug Hellmann wrote: [...] > We also discussed changing the CI interface to build docs to use > the "tox -e docs" command like contributors generally run locally. [...] Better still, something like `tox -e venv -- sphinx-build` would be more in keeping with

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-07 Thread Doug Hellmann
Excerpts from sfinucan's message of 2017-07-07 15:58:10 +0100: > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > remove the feature at this point. However, this is going to necessitate some > mechanical changes for most projects with docs and this mail serves as a

[openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-07 Thread sfinucan
tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just remove the feature at this point. However, this is going to necessitate some mechanical changes for most projects with docs and this mail serves as a heads up and request for input before we proceed. -- Since pretty much