From d1bb1d76daf30db46203a6f0a33490f4498e55ea Mon Sep 17 00:00:00 2001 From: whoami-rajat Date: Thu, 21 Feb 2019 00:35:07 +0530 Subject: [PATCH] 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 --- doc/source/contributor/api_microversion_dev.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/source/contributor/api_microversion_dev.rst b/doc/source/contributor/api_microversion_dev.rst index c9666ed1b80..073cb75efe4 100644 --- a/doc/source/contributor/api_microversion_dev.rst +++ b/doc/source/contributor/api_microversion_dev.rst @@ -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 -------------------------