Thanks for the feedback folks. We didn't do a formal vote, but it
seems we don't need one as so many are on the same page.

On Tue, May 7, 2019 at 10:06 PM José Carlos Chávez <[email protected]> wrote:
>
> +1 If kafka is killing support for 0.11 makes sense to deprecate 0.8
>
> José Carlos Chávez
>
>
> tir. 7. mai 2019 kl. 16:03 skrev Brian Devins-Suresh <[email protected]>:
>
> > +1 based on Jorge's response. My inclination is to follow what the major
> > vendors for each component are supporting with a bit of lag possibly.
> >
> > On Tue, May 7, 2019 at 4:36 AM Adrian Cole <[email protected]> wrote:
> >
> > > https://github.com/apache/incubator-zipkin/pull/2564 removes this and
> > the
> > > PR description includes text I plan to weave into the release notes.
> > >
> > > On 2019/05/07 00:48:52, Adrian Cole <[email protected]> wrote:
> > > > Hi, team.
> > > >
> > > > We are readying release announcement for Zipkin 2.13 (it is pending
> > > > IPMC vote still). I think we should say this is the last version we
> > > > publish Kafka 0.8 support.
> > > >
> > > > I can't find any support matrix from Kafka, but it is very old, almost
> > > > 4 years old since last release of Kafka 0.8. Removing this will
> > > > improve our build times which are close to the limits. It will also
> > > > reduce the size of our docker image and the complexity of creating it.
> > > >
> > > > Note that this does not mean remove Kafka, Just brokers before version
> > > 0.10.
> > > >
> > > > WDYT?
> > > > -Adrian
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to