On 02/16/2015 04:36 PM, Doug Hellmann wrote:
> When we talked about this in the review of the governance change to set
> "tox -e docs" as part of the testing interface for a project, jeblair
> (and maybe others) pointed out that we didn't want projects running
> extra steps when their docs were built. So maybe we want to continue to
> use "tox -e venv -- python setup.py build_sphinx" for the real docs, and
> allow a "tox -e docs" job for the check queu for testing.
trove has XML docs and sphinx (AFAIK), so calling build_sphinx will not
do everything.
Let me work on a patch for trove now...
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
