diff --git a/doc/source/releasing.rst b/doc/source/releasing.rst index 35bfb14..3e2ae00 100644 --- a/doc/source/releasing.rst +++ b/doc/source/releasing.rst @@ -22,9 +22,10 @@ that starts with DNM (Do Not Merge) to indicate that the change is just a test, or -2, if you have the right access permissions. It is also worth noting that every Stadium project will have a periodic job -running unit tests against the master version of neutron-lib +running unit tests and pep8 against the master version of neutron-lib (`periodic-neutron-py35-with-neutron-lib-master `_ -being an example). Checking Grafana's `periodic `_ +being an example). Checking Grafana's `periodic `_ dashboard can give you a glimpse into the sanity of the integration between neutron-lib and the Stadium projects, and can be considered the quick check -before going ahead with a full blown sentinel patch. +before going ahead with a full blown sentinel patch. Periodic failures can be +debugged by viewing the `periodic logs `_ diff --git a/doc/source/usage.rst b/doc/source/usage.rst index ca6e063..fcf5805 100644 --- a/doc/source/usage.rst +++ b/doc/source/usage.rst @@ -55,7 +55,8 @@ To adopt neutron-lib's hacking checks: ``enable-extensions`` in their ``tox.ini``. #. Actively adopt neutron-lib hacking checks by running and monitoring - the neutron-lib periodic job (as per `stadium guidelines + the neutron-lib `periodic job `_ (as per `stadium guidelines `_ and watching for announcements. Announcements regarding neutron-lib adopter hacking checks will be communicated via openstack-dev email list