openstack
/
nova-specs
Code Issues Proposed changes

Update the template to capture additional deployer impact info 

Add prompts to help a deployer understand if the change will
take immediate effect, or is something that has to be explicitly
configured into the system.  Generally a change that has
immediate effect would be of more concerns for both updates
and folks on the CI path than a change that is in effect dormant
until configured.

This also of course prompts for the BP submitter to also
consider the same issue, which is a topic that should be addressed
at design time.

Change-Id: I7e78ffcaec800bbfe09135d90069158dc6e58923
This commit is contained in:
Phil Day 2014-03-25 11:19:09 +00:00
parent 73b59b24b3
commit 95cee21ee4
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
specs/template.rst
View File

@ -111,6 +111,9 @@ such as:
implement as well)? Are the default values ones which will work well in
real deployments?
- Is this a change that takes immediate effect after its merged, or is it
something that has to be explicitly enabled?
- If this change is a new binary, how would it be deployed?
- Please state anything that those doing continuous deployment, or those