On Mon, Oct 3, 2016 at 11:29 PM, Joshua Hesketh <joshua.hesketh at gmail.com> wrote: > The question now is whether or not to continue running. Is there still > value in running turbo-hipster? It uses significant resources and it feels > that developers have learned the lessons it was designed to teach. > Is there any value in running turbo-hipster as a periodic job across multiple releases? One common request from operators is to be able to upgrade directly from, say, kilo to mitaka or newton. I know there are other factors involved in that (APIs, objects, etc), the question is if this is a necessary/useful component of testing that upgrade path? dt -- Dean Troyer dtroyer at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161004/0737296b/attachment.html>