Open Stack

To all third-party CI maintainers,

As you are aware, cinder third-party CI systems are required to run on 
all cinder changes.  However, the os-brick library used in cinder CI 
testing is the latest appropriate *released* version of os-brick.

Thus, it is possible for changes to be happening in os-brick development 
that might impact the functionality of your driver. If you aren't 
testing os-brick changes, you won't find out about these until *after* 
the next os-brick release, which is bad news all around.

Therefore, at last week's cinder midcycle [0], the cinder project team 
agreed to require that cinder third-party CI systems run on all os-brick 
changes in addition to all cinder changes.  This is a nice-to-have for 
the current (Zed) development cycle, but will be required in order for a 
driver to be considered 'supported' in the 2023.1 (Antelope) release [1].

If you have comments or concerns about this policy, please reply on the 
list to this email or put an item on the agenda [2] for the cinder 
weekly meeting.


[0] https://etherpad.opendev.org/p/cinder-zed-midcycles
[1] 
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_changes_should_I_test_on.3F
[2] https://etherpad.opendev.org/p/cinder-zed-meetings