opendev/infra-specs
Code Issues Proposed changes
infra-specs/doc/source
History
Wayne 924990fb9e Jenkins Job Builder 2.0.0 API Changes/Rewrite 
* to ensure that JJB classes are useful to third party users of the library
* to clearly define public interfaces for JJB classes and document the
  purpose/role of these classes in the API
* to eliminate unuseful class relationships in favor of rationally-tiered
  delegation of program behavior
* to reduce the importance of the YamlParser as the only source of data
  structures necessary for XML generation

Change-Id: I1f2e8c85654413f49d6a5fa61cd8d0c8b5ef5e03
2015-09-11 13:47:25 -07:00
..
conf.py
Use the current date for the copyright statement
2014-09-10 16:04:37 -04:00
contributing.rst
Initial commit
2014-06-10 16:25:32 -07:00
index.rst
Jenkins Job Builder 2.0.0 API Changes/Rewrite
2015-09-11 13:47:25 -07:00
readme.rst
Initial commit
2014-06-10 16:25:32 -07:00
specs
Initial commit
2014-06-10 16:25:32 -07:00
template.rst
Initial commit
2014-06-10 16:25:32 -07:00

readme.rst

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 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.