Modify the "Data model impact" section of the spec template to
so that the impact of a change on zero-downtime database migrations
will be addressed.
Change-Id: I1ad5ad4ff333aef66ce80b442d8290982160c1c8
Depends-On: Ic8b21d2cc1e42f3e1478973df0f80792e5098f90
Partially-Implements: blueprint rolling-upgrades
When this template was created, the intention behind this section was to
know the got-to people for specific specs. Questions like: Who should I
ping if I need more Glance insights? Who should I ping to actually get
reviews? etc
Unfortunately, The reviewers section has turned to a field mostly used
to highlight people interested in a specific feature. More often than
not, the revieweres listed in this section are not the ones reviewing
the patches for the spec.
In addition to the above, this section currently separates core
reviewers from non-cores. This separation brings no value to this
section nor the spec itself.
Regardless the size of the team, this section is not bringing any value
to the process as reviewers not in this list can as well review the
patches as much as the reviewers listed there can also not review the
patches.
Change-Id: I973d97e82f4561de8d4ac33672494eae0fc15925
Goal is to maintain API specs in the specs repo for each project
and to eliminate the image-api repo.
Splits up original v2 API document into multiple files.
Change-Id: I7b6fbb1ee4a9a2e04395a7aa942d9ebdb011cc85
Adds a requirement for an APIImpact flag in
the commit message for a proposed spec if it proposes
changes to the Glance REST API. This will make it
much easier for people such as the API WG who want to
review API changes across OpenStack to find and
review proposed API changes.
Change-Id: Ic83a797b3feae28052abba78ac9abc4a07f4063e
This patch adds "Reviewers" subsection under the "Implementation"
section in the template. Thus, all the specs following this commit
would need to suffice the Reviewers requirement for the approval.
Email [0] sent to the ML, corresponding to this requirement.
[0] http://lists.openstack.org/pipermail/openstack-dev/2014-October/048918.html
Change-Id: I396b7fad247a2e115bf9c7b7634240c15355ab20
* The template is located in specs/ directory and not in doc/source/specs/
* The current reST renderer link in the template file points to an
expired domain
Change-Id: I165fe6a8eabb59d0918ada6c7ce24d4ea095544d
Brian Rosmaita