On Fri, Dec 15, 2017 at 11:39:16AM -0700, Alex Schultz wrote: > Perhaps we can start reviewing the items and those with little to no > impact we can merge for the remainder of the cycle. I know > realistically everything has an impact so it'll be >0, but lets try > and keep it as close to 0 as possible. I know we've already merged > some arch support stuff this cycle but it does seem doubtful that > it'll be properly fully supported in TripleO by the end of Queens. I > think it best to leave the blueprint slated for Rocky-1 unless we get > some sudden movement on patches. Please continue to propose patches > for review and let's make sure they work in a backwards compatible > fashion with extra eyes on upgrade impacts.
Okay. We'll do our best and see where we get to. In the meantime I'll start a related, but seperate thread to talk through the design issues for the multi-arcgh images and containers to try and focus development when we get there ;P Yours Tony. __________________________________________________________________________ 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
