Hi Sergey, As Gorka said, we generally don't require spec for driver features but we encourage to register a blueprint on launchpad[1] so as to keep track of all the features. Having said that, the spec would act as a good point of documentation so we can consider it merging. It's a good point for discussion which i will add it in the cinder meeting agenda today[2] but even if it doesn't merge this cycle (since we're already in the spec freeze exception phase), we can do it next cycle without blocking reviews of the main feature. [1] https://blueprints.launchpad.net/cinder [2] https://etherpad.opendev.org/p/cinder-zed-meetings Thanks and regards Rajat Dhasmana On Tue, Jul 5, 2022 at 2:19 PM Sergey Drozdov <sergey.drozdov.dev@gmail.com> wrote:

To whom it may concern,

I am helping a colleague of mine with the following pieces of work: 820027 (https://review.opendev.org/c/openstack/cinder/+/820027), 820030 ( https://review.opendev.org/c/openstack/cinder-specs/+/820030). I was wondering whether it is not too late to include the aforementioned within the Zed release? Is there anyone who can advise on this matter?

Best Regards, Sergey