openstack
/
cinder
Code Issues Proposed changes

Update section 'When do i need a new Microversion?' 

It is been agreed upon that if a new feature is proposed
sharing similarities (in terms of intention and code)
with a previously merged feature then both the features
can be clubbed together within the same (previous feature)
microversion given that the previously merged feature isn't
released.

Change-Id: I80216f9c2645ece1ea4c57550936a247440a5a82
This commit is contained in:
whoami-rajat 2019-02-21 00:35:07 +05:30 committed by Rajat Dhasmana
parent cf306ff52f
commit d1bb1d76da
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/contributor/api_microversion_dev.rst
View File

@ -126,6 +126,11 @@ we need a microversion".
{rank=min; silent_fail}
}
If a patch that will require a microversion increment is proposed
having similar intention and code with a previously merged patch
given the previous merged patch hasn't been released, then the
previously merged patch could be modified to include the new patch
code under the same microversion.
**Footnotes**
@ -289,6 +294,11 @@ necessary to add changes to other places which describe your change:
should indicate which microversion is required for the change, and it should
refer to the numerical value of the microversion and not its constant name.
* Update the ``version`` parameter in api-ref responses here ``cinder/api-ref/
source/v3/samples/versions/version-show-response.json`` and here
``cinder/api-ref/source/v3/samples/versions/versions-response.json``
to the latest microversion to avoid functional test failure.
Allocating a microversion
-------------------------