29ecd4b277
This commit copies some changes from the nova-specs repo. This fixes a couple of issues around the tox.ini file and the setup.cfg to make running a docs build infra job work well and catch formatting failures. The nova-specs commits this is based on: 4a6cb70 Make sphinxbuild fail on formatting errors 775d690 Allow running 'tox' with no arguments 8947230 Disable site-packages for tox Change-Id: If416c68e9a608039e74cadb2d50915fa6b859d89
QA Specs Repository
This is a git repository for doing design review on QA enhancements as part of the OpenStack program. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.
Repository Structure
The expected structure of the respository is as follows:
specs/
implemented/Expected Work Flow
- Create a blueprint stub in
tempestblueprint repository - Propose review to qa-specs repository (ensure bp:blueprint_name is in the commit message
- Link
Read the full specificationto the gerrit address of the spec - Bring forward the proposed item to the openstack-qa meeting for summary
- Review happens on proposal by qa-core members, and others
- Iterate until review is Approved or Rejected
Once a Review is Approved...
- Update blueprint, Copy summary text of blueprint to there
- Link
Read the full specificationto the git address of the spec - Profit!
Revisiting Specs
We don't always get everything right the first time. If we realize we need to revisit a specification because something changed, either we now know more, or a new idea came in which we should embrace, we'll manage this by proposing an update to the spec in question.
Learn as we go
This is a new way of attempting things, so we're going to be low in process to begin with to figure out where we go from here. Expect some early flexibility in evolving this effort over time.