093a9d6244
sphinx complains about: " source/specs/task-tracker.rst:231: WARNING: Pygments lexer name u'storyboard-migration' is not known checking consistency: ... source/specs/logs-in-swift.rst:: WARNING: document isn't included in any toctree ... source/specs/maniphest.rst:: WARNING: document isn't included in any toctree" Fix these warnings, the next pbr release will stop again on errors, so prepare for that. Fixes are: * Add toc that includes the two files und new section "Abandoned" * Fix code-block usage for task-tracker Change-Id: I6df505e2eb1aa5ff76b2a9d0041de8763ca421a7
Infra Specs Repository
This is a git repository for doing design review on enhancements to the OpenStack Project Infrastructure. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.
Expected Work Flow
- Create a story in StoryBoard with a task
affecting the
infra-specsproject. - Propose a change to infra-specs repository (ensure Story:<story number> is in the commit message).
- Leave a comment on the story with the Gerrit URL of the specification.
- Review happens on proposal by infra-core members and others.
- When ready for final approval, bring forward the proposed item to the infra meeting.
Once a specification is approved...
- Update story, copy summary text of specification to there.
- Leave a comment to the git address of the specification.
Revisiting Specifications
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 specification in question.