On 06/06/2018 11:35 AM, Jeremy Stanley wrote:
On 2018-06-06 18:24:00 +0200 (+0200), Dmitry Tantsur wrote:
In Ironic world we run doc8 on README.rst as part of the pep8 job.
Maybe we should make it a common practice?
[...]
First, the doc8 tool should be considered generally useful for any
On 2018-06-06 18:24:00 +0200 (+0200), Dmitry Tantsur wrote:
> In Ironic world we run doc8 on README.rst as part of the pep8 job.
> Maybe we should make it a common practice?
[...]
First, the doc8 tool should be considered generally useful for any
project with Sphinx-based documentation,
Excerpts from Dmitry Tantsur's message of 2018-06-06 18:24:00 +0200:
> In Ironic world we run doc8 on README.rst as part of the pep8 job. Maybe we
> should make it a common practice?
That seems like it may be a good thing to add, but I don't know
that it is sufficient to detect all of the
In Ironic world we run doc8 on README.rst as part of the pep8 job. Maybe we
should make it a common practice?
On 06/06/2018 03:35 PM, Jeremy Stanley wrote:
On 2018-06-06 16:36:45 +0900 (+0900), Akihiro Motoki wrote:
[...]
In addition, unfortunately such checks are not run in project gate,
so
On 2018-06-06 16:36:45 +0900 (+0900), Akihiro Motoki wrote:
[...]
> In addition, unfortunately such checks are not run in project gate,
> so there is no way to detect in advance.
> I think we need a way to check this when a change is made
> instead of detecting an error when a release patch is
Hi the release team,
When I prepared neutron Rocky-2 deliverables, I noticed a new metadata
syntax check
which checks README.rst was introduced.
As of now, README.rst in networking-bagpipe and networking-ovn hit this [1].
Although they can be fixed in individual projects, what is the current
