openstack
/
openstack
Code Issues Proposed changes

Update git submodules 

* Update placement from branch 'master'
  - Merge "Initial structure for in-tree specs"
  - Initial structure for in-tree specs
    
    We decided in IRC and email discussions that henceforth
    placement specs will reside in the same tree as code and docs.
    This change sets that up using the following structure:
    
    * There is a docs/source/specs top-level index that should be
      updated with each release to include tables of contents generated
      from cycle directories (currently pointing to train) for
      approved and implemented specs.
    
    * In the approved directory for any cycle there will be a
      <cycle-template>.rst file to use as the basis for any new
      spec. New specs go in this directory.
    
    * In the implemented directory is a placeholder file which
      will be removed when the first (if any) spec moves from
      approved (meaning in-progress) to implemented. The PTL
      or their designee will be responsible for doing that moving.
      The placeholder file is required to avoid warnings (which
      will kill the tox docs job) from the table of contents
      globbing.
    
    * The train-template.rst is a copy-with-edits from nova's
      version of the same thing. The main changes are to indicate
      that StoryBoard, not launchpad blueprints, are the starting
      point and to remove various nova-isms.
    
      It is likely we will want to further tweak the template as
      we decide what matters.
    
    The next steps for this are for people with placement specs
    that had been pending in nova in stein, to resubmit them to
    placement as train specs (in doc/source/specs/train/approved).
    It is quite likely and not surprising that it will sometimes
    be confusing whether a spec should be in nova or placement.
    Ideally we can identify the "just placement" aspects of a
    change and make a placement-only spec for that which the nova
    spec makes reference to. This may sound like a pain but it is
    a feature, not a bug, which helps make sure that placement
    evolves its API as a strong contract for all potential clients.
    
    Change-Id: I85854d771409701cea2fcf7a218f02af60dba72e
This commit is contained in:
Zuul 2019-03-25 23:24:32 +00:00 committed by Gerrit Code Review
parent a30f7f7d0d
commit f2acca3a32
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
placement

@ -1 +1 @@
Subproject commit c99492cfc635a1d9faccc3e71878f903f2b4587e
Subproject commit 02fb9cf8c754f1b39009d6f106e9e1e1a373af26