# Avoiding compatibility issues in OpenStack Cinder Xena (linstor volume driver)

**URL:** <https://forums.linbit.com/t/avoiding-compatibility-issues-in-openstack-cinder-xena-linstor-volume-driver/1105>\
**Category:** General\
**Tags:** openstack\
**Created:** [December 15, 2025, 1:17pm UTC](https://forums.linbit.com/t/avoiding-compatibility-issues-in-openstack-cinder-xena-linstor-volume-driver/1105 "2025-12-15T13:17:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mojtabashg](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@mojtabashg](https://forums.linbit.com/u/mojtabashg)\
**Post date:** [December 15, 2025, 1:17pm UTC](https://forums.linbit.com/t/avoiding-compatibility-issues-in-openstack-cinder-xena-linstor-volume-driver/1105/1 "2025-12-15T13:17:56Z")

</div>

hello everyone,  
We are currently using **OpenStack Cinder (Xena release)** and we aren’t able to upgrade our cluster at this time. Based on my understanding and after reviewing your documentation, it appears that the latest changes are actively implemented and maintained only on the following your stable branches:

- stable/2024.1, stable/2024.2, stable/20245.1

with this situation, could you please advise on the **best recommended approach** to proceed **without introducing side effects or compatibility issues**?  
In particular, would approaches such as **git cherry-picking specific commits** from the maintained branches , or do you recommend an alternative method?

Thank you in advance for your guidance