notification = of course relase note with information and upgrade info = of course 1 full release of supporting both heka and alternative = not so much On 29 September 2016 at 10:54, Swapnil Kulkarni (coolsvap) <me at coolsvap.net> wrote: > On Sep 29, 2016 3:06 PM, "Christian Berendt" > <berendt at betacloud-solutions.de> wrote: >> >> > On 29 Sep 2016, at 06:26, Steven Dake (stdake) <stdake at 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-request at lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > Kolla is an operator tool and there are multiple tools only internal to > deployment. This does not mean we can deprecate tools without operator being > notified about it. > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >