+1 (non binding), thanks Ismael! El jue., 19 abr. 2018 a las 13:01, Manikumar (<manikumar.re...@gmail.com>) escribió:
> +1 (non-binding). > > Thanks. > > On Thu, Apr 19, 2018 at 3:07 PM, Stephane Maarek < > steph...@simplemachines.com.au> wrote: > > > +1 (non binding). Thanks Ismael! > > > > On Thu., 19 Apr. 2018, 2:47 pm Gwen Shapira, <g...@confluent.io> wrote: > > > > > +1 (binding) > > > > > > On Wed, Apr 18, 2018 at 11:35 AM, Ismael Juma <ism...@juma.me.uk> > wrote: > > > > > > > Hi all, > > > > > > > > I started a discussion last year about bumping the version of the > June > > > 2018 > > > > release to 2.0.0[1]. To reiterate the reasons in the original post: > > > > > > > > 1. Adopt KIP-118 (Drop Support for Java 7), which requires a major > > > version > > > > bump due to semantic versioning. > > > > > > > > 2. Take the chance to remove deprecated code that was deprecated > prior > > to > > > > 1.0.0, but not removed in 1.0.0 (e.g. old Scala clients) so that we > can > > > > move faster. > > > > > > > > One concern that was raised is that we still do not have a rolling > > > upgrade > > > > path for the old ZK-based consumers. Since the Scala clients haven't > > been > > > > updated in a long time (they don't support security or the latest > > message > > > > format), users who need them can continue to use 1.1.0 with no loss > of > > > > functionality. > > > > > > > > Since it's already mid-April and people seemed receptive during the > > > > discussion last year, I'm going straight to a vote, but we can > discuss > > > more > > > > if needed (of course). > > > > > > > > Ismael > > > > > > > > [1] > > > > https://lists.apache.org/thread.html/dd9d3e31d7e9590c1f727ef5560c93 > > > > 3281bad0de3134469b7b3c4257@%3Cdev.kafka.apache.org%3E > > > > > > > > > > > > > > > > -- > > > *Gwen Shapira* > > > Product Manager | Confluent > > > 650.450.2760 <(650)%20450-2760> | @gwenshap > > > Follow us: Twitter <https://twitter.com/ConfluentInc> | blog > > > <http://www.confluent.io/blog> > > > > > >
