openstack/cinder
Code Issues Proposed changes

Add statement about CI for backports

Browse Source 
Back in February, the cinder project announced a policy that we'd
like to see CI results documented on driver backports:
http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027021.html

Bring this info into the contributor documentation.

Change-Id: Ide112de44887c031cf160e30dbdfe083c1998bda
This commit is contained in:
Brian Rosmaita 2022-04-20 12:50:24 -04:00
parent ff022d5a67
commit b45379de37
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/source/contributor/backporting.rst
View File

@ -73,3 +73,22 @@ In fact, maybe *too* easy. Here are some guidelines:
If you have questions about any of this, or if you have a bug to fix that If you have questions about any of this, or if you have a bug to fix that
is only present in one of the stable branches, ask for advice in is only present in one of the stable branches, ask for advice in
``#openstack-cinder`` on IRC. ``#openstack-cinder`` on IRC.
Backport CI Testing
-------------------
Like all code changes, backports should undergo continuous integration
testing. This is done automatically by Zuul for changes that affect the
main cinder code.
When a vendor driver patch backport is proposed, we would like to
see a clear statement on the gerrit review that the patch has been
tested in an appropriate environment.
This shouldn't be a big deal because presumably you've done local
testing with your backend to ensure that the code works as expected in a
stable branch; we're simply asking that this be documented on the backport.
A good example of how to document this can be found on
`https://review.opendev.org/c/openstack/cinder/+/821893/
<https://review.opendev.org/c/openstack/cinder/+/821893/3#message-ade9aa6ad8bd99fefab908c777fe106e907c7636>`_.