The thread on the dev list is already too long for my liking. I hope there will be a TL;DR in the dev mailing list digest. Tomas
-----Original Message----- From: arkady.kanev...@dell.com [mailto:arkady.kanev...@dell.com] Sent: Thursday, December 14, 2017 3:40 AM To: mrhills...@gmail.com; fu...@yuggoth.org; openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] thierry's longer dev cycle proposal It is a sign of the maturity of OpenStack. With lots of deployment and most of them in production, the emphasis is shifting from rapid functionality additions to stability, manageability, and long term operability. -----Original Message----- From: Melvin Hillsman [mailto:mrhills...@gmail.com] Sent: Wednesday, December 13, 2017 5:29 PM To: Jeremy Stanley <fu...@yuggoth.org>; openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] thierry's longer dev cycle proposal I think this is a good opportunity to allow some stress relief to the developer community and offer space for more discussions with operators where some operators do not feel like they are bothering/bugging developers. I believe this is the main gain for operators; my personal opinion. In general I think the opportunity costs/gains are worth it for this and it is the responsibility of the community to make the change be useful as you mentioned in your original thread Thierry. It is not a silver bullet for all of the issues folks have with the way things are done but I believe that if it does not hurt things and offers even a slight gain in some area it makes sense. Any change is not going to satisfy/dis-satisfy 100% of the constituents. -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: +1 (832) 264-2646 irc: mrhillsman On 12/13/17, 4:39 PM, "Jeremy Stanley" <fu...@yuggoth.org> wrote: On 2017-12-13 22:35:41 +0100 (+0100), Thierry Carrez wrote: [...] > It's not really fait accompli, it's just a proposal up for discussion at > this stage. Which is the reason why I started the thread on -dev -- to > check the sanity of the change from a dev perspective first. If it makes > things harder and not simpler on that side, I don't expect the TC to > proceed. [...] With my TC hat on, regardless of what impression the developer community has on this, I plan to take subsequent operator and end-user/app-dev feedback into account as well before making any binding decisions (and expect other TC members feel the same). -- Jeremy Stanley _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
