On Thu, Aug 02, 2018 at 05:59:20PM +0200, Radomir Dopieralski wrote: > To be honest, I don't see much point in automatically creating bugs that > nobody is going to look at. When you implement a new feature, it's up to > you to make it available in Horizon and CLI and wherever else, since the > people working there simply don't have the time to work on it. Creating a > ticket will not magically make someone do that work for you. We are happy > to assist with this, but that's it. Anything else is going to get added > whenever someone has any free cycles, or it becomes necessary for some > reason (like breaking compatibility). That's the current reality, and no > automation is going to help with it. >
I don't think that's universally true with these projects. There are some on these teams that are interested in implementing support for new features and keeping existing things working right. The reality for most of this then is new features won't be available and users will move away from using something like Horizon for whatever else comes along that will give them access to what they need. I know there are very few developers focused on Cinder that also have the skillset to add functionality to Horizon. I agree ideally someone would work on things wherever they are needed, but I think there is a barrier with skills and priorities to make that happen. And at least in the case of Cinder, neither Horizon nor OpenStackClient are required. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
