-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, September 29, 2016 at 8:59 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [Kolla] Deprecation Policies (related to Heka)
notification = o
On Sep 29, 2016 9:30 PM, "Michał Jastrzębski" wrote:
>
> 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)
> wrote:
> > On Sep 2
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)
wrote:
> On Sep 29, 2016 3:06 PM, "Christian Berendt"
> wrote:
>>
>> > On 29 Sep 2016
On Sep 29, 2016 3:06 PM, "Christian Berendt"
wrote:
>
> > On 29 Sep 2016, at 06:26, Steven Dake (stdake) 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 th
Tagging kolla
On 29/09/16 16:22, Michał Jastrzębski wrote:
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 Sep
