)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"2b8233bd8f370a2739d920ce59887aaa73638ba9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"5f51d053_4bdadc04","updated":"2022-07-07 10:54:35.000000000","message":"\u003e Patch Set 2:\n\u003e \n\u003e \u003e Patch Set 2: Code-Review-1\n\u003e \u003e \n\u003e \u003e Thanks for the patch! However, it\u0027s worth remembering that there are people out there who use python-openstackclient to talk to a variety of openstack clouds, some of which still run older versions of openstack. It is out of the control of those users as to what version of openstack their providers run.\n\u003e \u003e \n\u003e \u003e It has long been the stance of openstackclient and openstacksdk that we exist in support of the end-users, and as such should continue to support older versions of openstack as best we can. This is one of the ways in which openstacksdk/openstackclient present a superior user experience to python-*client.\n\u003e \u003e \n\u003e \u003e There isn\u0027t much gained by deleting support that exists - and we may very well have users who depend on it.\n\u003e \n\u003e Is the \"how long\" documented? Every support is bound to end at some point, so, for example, could volume v1 be remove in two new major versions of OSC?\n\nI don\u0027t think we\u0027ll ever delete this. It cost us almost nothing to maintain this support and as long as there\u0027s anyone using it, we should keep it around IMO","commit_id":"ef4ccdac3b7c63c5e7c5f5973f282200a3899f6b"}]}