Just saw some of your comments (great, thanks), and I'll weigh in if I come up with a cogent input.
I'd really like to see Bloomberg, RAX, and Cirrus7, Huawei, and other ops folks respond. I suspect this is already a fait accompli but there are many details (as you mentioned already in one posting about mid-cycles) to work out. On Wed, Dec 13, 2017 at 11:53 AM, Sean McGinnis <sean.mcgin...@gmx.com> wrote: > Would be great to get ops-side input. I didn't want to cross-post because > I'm > sure this is going to be a big thread and go on for a while. But I would > encourage anyone with input to jump in on that thread. We could also > discuss it > separately here and I can try to answer questions or feed that input back > in to > the -dev side. > > Sean > > On Wed, Dec 13, 2017 at 11:48:01AM -0700, David Medberry wrote: > > Hi all, > > > > Please read Thierry's email to the openstack-dev list this morning and > > follow the thread (getting long already just two hours in.) > > > > This references some ideas and concerns that have come from the Ops > > community, but this is specifically a -dev thread (but I suspect a lot of > > ramifications for ops as well.) > > > > http://lists.openstack.org/pipermail/openstack-dev/2017- > December/125473.html > > > > title is: > > Switching to longer development cycles > > (and if you are sub'd to openstack-dev you will find it in there.) > > > > > > The thread of emails is at least 10+ deep already with folks weighing in > on > > all sides of the aisle. > > > > -dave > > > _______________________________________________ > > 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
