283d14329f
Per discussion in the most recent Infrastructure team meeting: http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-06-06-19.03.html ...the following specifications should be considered completed and so are being moved into the implemented subsection of the index: complete-reviewable-release-automation ethercalc neutral-governance-website publish-election-repo releases-openstack-org shade These specs had some parts which were not completed for various reasons and became out of scope, so have been adjusted slightly to stop mentioning the missing features and moved into implemented: deploy-stackviz unified_mirrors Change-Id: Ia603a1f752e0c8acb43ed323864267c2b69bdf03
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.