Agree with Christian, this is our internal wiring. As long as we provide automated upgrade procedure which will seamlessly migrate from heka to alternative we want, we should be good without deprecation per se.
Cheers, Michal On 29 September 2016 at 04:36, Christian Berendt <bere...@betacloud-solutions.de> wrote: >> On 29 Sep 2016, at 06:26, Steven Dake (stdake) <std...@cisco.com> wrote: >> >> If you have a different parsing of the deprecation policy, feel free to >> chime in. > > Heka is only used as an internal component of Kolla and is not provided as a > service for the operators. It should be sufficient to replace Heka by > something else without deprecating it. > > Christian. > > __________________________________________________________________________ > 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 > __________________________________________________________________________ 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
