opendev/infra-specs
Code Issues Proposed changes
OpenStack Infrastructure Blueprint Repository
101 Commits 1 Branch 0 Tags 4.4 MiB
Python 100%
df8e26261b
Go to file
Doug Hellmann df8e26261b cleanups for centralize-release-tagging 
Fix a typo and markup issue in the existing spec

Change-Id: I789384daa14ceaecab709595acec2a7b37aee1fe
2015-07-07 19:08:43 +00:00
doc/source Centralize Release Tagging 2015-07-02 14:32:47 +00:00
specs cleanups for centralize-release-tagging 2015-07-07 19:08:43 +00:00
.coveragerc Initial commit 2014-06-10 16:25:32 -07:00
.gitignore Initial commit 2014-06-10 16:25:32 -07:00
.gitreview Added .gitreview 2014-05-20 16:36:13 +00:00
.mailmap Initial commit 2014-06-10 16:25:32 -07:00
.testr.conf Initial commit 2014-06-10 16:25:32 -07:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 11:56:28 -08:00
LICENSE Initial commit 2014-06-10 16:25:32 -07:00
MANIFEST.in Initial commit 2014-06-10 16:25:32 -07:00
README.rst Add priority efforts section 2015-05-14 15:30:50 -07:00
requirements.txt Add RSS feed 2014-09-10 16:04:35 -04:00
setup.cfg Initial commit 2014-06-10 16:25:32 -07:00
setup.py Initial commit 2014-06-10 16:25:32 -07:00
template.rst Add Gerrit Topic to the spec template 2015-03-03 11:18:10 -08:00
test-requirements.txt Initial commit 2014-06-10 16:25:32 -07:00
tox.ini 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.