Add clarification about re-proposing specs

Make it clear that previously approved but unimplemented specs must
be re-proposed for the current release.

Change-Id: Ibe3da75827b340218ae1777615c5edb8dcec57f5
This commit is contained in:
Brian Rosmaita 2020-11-09 21:50:03 -05:00
parent 873135ff05
commit 98f490651d
2 changed files with 12 additions and 7 deletions

View File

@ -26,9 +26,10 @@ Specifications are proposed for a given release by adding them to the
status of a blueprint for a given release can be found by looking at the
blueprint in launchpad. Not all approved blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be
quick, but even if something was previously approved, it should be re-reviewed
to make sure it still makes sense as written.
**Previously approved specifications must be re-proposed for a new release.**
The review will most likely be quick, but we need to make sure that everyone
still understands the spec as written, and that it still fits in with the
project's plans.
Prior to the Juno development cycle, this repository was not used for spec
reviews. Reviews prior to Juno were completed entirely through Launchpad

View File

@ -135,10 +135,14 @@ Untargeted specs
.. note::
The following specs are ones that have been approved but have
not been completed in the planned release. Rather than leave
them in the originally planned release or remove them, they
should be made untargeted for future reference.
The following specs have been approved but have not been completed
in the originally planned release. Rather than remove them, they
have been made 'untargeted' for future reference. If you would like
to work on one of these specs, please re-propose it for the appropriate
release. The review will most likely be quick, but we need to make sure
that everyone still understands the spec as written, and that it still
fits in with the Cinder project's plans.
.. toctree::
:glob: