
Forbidden aggregates was added in microversion 1.32 (part of Train) and allocation candidates mappings was added in 1.34 so those specs have been moved to implemented. An _extra/.htaccess is added to redirect the approved spec to the implemented spec. If we're experiencing enough volume of specs to warrant automating this, it should be easy to do, but at this point we don't have, nor intend to have, large numbers of specs. While doing that I noticed the management of spec documents can be simplified somewhat by moving placeholders and templates to a non-release specific location. The placeholder can then be used as a symlink when in approved or implemented when those are first created or otherwise empty (an empty directory when doing a table of contents glob is an error so some kind of file is needed). Contribution docs are updated to reflect the location of the template.rst file. The template.rst file is updated to be release generic. Change-Id: Icb886d5062a52bfc757ed7bbe36ed8a63abe1387
910 B
910 B
Placement Specifications
Train
Implemented
train/implemented/*
In Progress
train/approved/*
placeholder.rst template.rst