Most Kilo python-cinderclient changes not picked up in Kilo

[John Haller]

Many Kilo-related commits to python-cinderclient did not get picked up in the Kilo cinder client. See the list of commits which have only gone into Liberty:
http://lists.openstack.org/pipermail/openstack-dev/2015-April/062187.html

While I did not extensively look at all of the changes, at least this change did not make it into Kilo cinder:
https://review.openstack.org/#/c/114706/ (os-volume-type-access)
The above change was merged on February 2, while the last client tag before Liberty was made in September 26, 2014, 1.1.1.

[John Griffith (john-griffith)]

Yep, unfortunately there was never a cinderclient release during Kilo until after Kilo was cut. That's why none of the changes from the Kilo cycle are showing up for you, they're not there.

You'll need to do a pip install of the client that was pushed after the K release.

[John Griffith (john-griffith)]

Hate to mark invalid, but there's an option to get around it, and there's no way to go back in time and push a release to pypi.

[Alan Pevec (apevec)]

There's stable/kilo branch https://github.com/openstack/python-cinderclient/commits/stable/kilo
and you could release 1.1.x from that branch e.g. keystone client released 1.3.1 from stable/kilo recently.

Liberty releases won't work for distros due to updated dependencies which cannot be satisified when rest of the packages are Kilo.

Heatclient is in the same position and they're trying to push newer release to Kilo, but it's unclear how that would work now that stable/kilo have been branched: https://review.openstack.org/182672