Andreas Jaeger 62e8202e61 Update requirements for Sphinx 1.5
Update requirements to current global-requirements including Sphinx 1.5.
Add pbr as requirement.
Use update-requirements from requirements repo to sync content.

Migrate pbr's obsolete warnerrors to Sphinx' warning-is-error.
Fix any sphinx problems.

Change-Id: Id7d5783c5d5c1077d03ddcb18d813699561579e3
2017-03-02 19:11:26 +01:00
2017-03-02 19:11:26 +01:00
2014-06-10 16:25:32 -07:00
2014-05-20 16:36:13 +00:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2015-11-16 16:37:06 +00:00
2017-03-02 19:11:26 +01:00
2017-03-02 19:11:26 +01:00
2014-06-10 16:25:32 -07:00

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

  1. Create a story in StoryBoard with a task affecting the infra-specs project.
  2. Propose a change to infra-specs repository (ensure Story:<story number> is in the commit message).
  3. Leave a comment on the story with the Gerrit URL of the specification.
  4. Review happens on proposal by infra-core members and others.
  5. When ready for final approval, bring forward the proposed item to the infra meeting.

Once a specification is approved...

  1. Update story, copy summary text of specification to there.
  2. 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.

Description
OpenStack Infrastructure Blueprint Repository
Readme 4.4 MiB
Languages
Python 100%