Remove releasenotes/requirements.txt
In change Iaa917d4f126d24c701cd3b8b0edfba4d4e0ca9c1 we have the proposal to not to install releasenotes/requirements.txt as projects should not really need any extra requirements to produce releasenotes other than reno itself being installed and available. Remove the references to this requirements.txt file so the CI implementation does not get out of sync with policy. As noted by AJaeger in the other change, not repo uses this as yet. Change-Id: Ieab3dfde7854d76dded6b1f8dd3aab1f1071b208 Needed-by: Iaa917d4f126d24c701cd3b8b0edfba4d4e0ca9c1
This commit is contained in:
parent
a83231dd15
commit
f06f383a24
|
@ -80,15 +80,9 @@ To support releasenotes generation, projects should:
|
|||
``releasenotes/source/conf.py``.
|
||||
* Optionally list distro package pre-reqs for dependencies in ``bindep.txt``
|
||||
using the ``releasenotes`` tag.
|
||||
* Optionally list requirements needed in ``releasenotes/requirements.txt``.
|
||||
The list of requirements is:
|
||||
|
||||
* Sphinx
|
||||
* reno
|
||||
* openstackdocstheme
|
||||
|
||||
Assuming requirements have been properly installed, the following command
|
||||
should work with no addiitonal setup and should result in the releasenotes
|
||||
should work with no additional setup and should result in the releasenotes
|
||||
being emitted into ``releasenotes/build/html``.
|
||||
|
||||
.. code-block:: bash
|
||||
|
|
|
@ -170,8 +170,6 @@ developer convenience that should:
|
|||
|
||||
* Either install any needed distro dependencies from the ``releasenotes`` tag
|
||||
in ``bindep.txt`` or emit an error if they are not installed.
|
||||
* Install Python dependencies for Sphinx from
|
||||
``releasenotes/requirements.txt``.
|
||||
* Execute: ``sphinx-build -a -E -W -d releasenotes/build/doctrees -b html releasenotes/source releasenotes/build/html``
|
||||
|
||||
The project infrastructure will not use :code:`npm run releasenotes` to build
|
||||
|
|
Loading…
Reference in New Issue