Hi Apurva, I agree about KIP-185 (assuming the vote passes). To clarify, my list was not meant to be exhaustive, just the items with highest compatibility impact justifying the major bump. I expect we will have many other great KIPs. :)
Ismael On 10 Nov 2017 12:57 am, "Apurva Mehta" <apu...@confluent.io> wrote: I think this is a good idea and your proposed changes look good. I also think that this might be a good time to adopt KIP-185 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP- 185%3A+Make+exactly+once+in+order+delivery+per+partition+ the+default+producer+setting), and make the idempotent producer the default mode. We missed the window on 1.0.0 because we hadn't completed necessary work. But we should have it done by June 2018. Thanks, Apurva On Thu, Nov 9, 2017 at 4:10 AM, Ismael Juma <isma...@gmail.com> wrote: > That's correct, Tom. We can only remove deprecated APIs in major releases > since it's a breaking change. > > Ismael > > > On 9 Nov 2017 11:48 am, "Tom Bentley" <t.j.bent...@gmail.com> wrote: > > Hi Stephane, > > I think the version number rules are based on semantic versioning, so Kafka > can't remove even deprecated APIs in a minor release (it is a breaking > change, after all). Therefore until Kafka 2.0 we will have to carry the > weight of the deprecated APIs, and Java 7. > > Cheers, > > Tom > > > > On 9 November 2017 at 11:04, Stephane Maarek <steph...@simplemachines.com. > au > > wrote: > > > I'm very happy with the milestones but worried about the versioning > number. > > It seems it will mostly bring stuff out of deprecation vs actually > bringing > > in breaking features. A 2.0 to me should bring something major to the > > table, possibly breaking, which would justify a big number hop. I'm still > > new to software development in the oss, but that's my two cents > > > > On 9 Nov. 2017 8:44 pm, "Ismael Juma" <ism...@juma.me.uk> wrote: > > > > > Hi all, > > > > > > I'm starting this discussion early because of the potential impact. > > > > > > Kafka 1.0.0 was just released and the focus was on achieving the > original > > > project vision in terms of features provided while maintaining > > > compatibility for the most part (i.e. we did not remove deprecated > > > components like the Scala clients). > > > > > > This was the right decision, in my opinion, but it's time to start > > thinking > > > about 2.0.0, which is an opportunity for us to remove major deprecated > > > components and to benefit from Java 8 language enhancements (so that we > > can > > > move faster). So, I propose the following for Kafka 2.0.0: > > > > > > 1. It should be released in June 2018 > > > 2. The Scala clients (Consumer, SimpleConsumer, Producer, SyncProducer) > > > will be removed > > > 3. Java 8 or higher will be required, i.e. support for Java 7 will be > > > dropped. > > > > > > Thoughts? > > > > > > Ismael > > > > > >
