I'm not. There was a decent amount of time between the first 0.8 and 0.9 release.
On Wed, Feb 8, 2017, 12:08 PM Raghu Angadi <[email protected]> wrote: > True. > > I was commenting on Kafka developers. I am surprised the api breakages > didn't have any deprecation period at all. > > On Wed, Feb 8, 2017 at 12:02 PM, Xu Mingmin <[email protected]> wrote: > > > i tend to have more versions supported, actually in our prod environment, > > there're 0.8, 0.9 and 0.10 for different teams. we'd take care of users > > who are on old versions. > > > > > > On Wed, Feb 8, 2017 at 10:56 AM, Raghu Angadi <[email protected] > > > > wrote: > > > > > If we let the user pick their kafka version in their dependencies, > > simplest > > > fix is to broaden KafkaIO kafka-client dependency to something like > > [0.9.1, > > > 0.11) (and handle the api incompatibility at runtime). > > > > > > It might not be long before we could drop 0.9 support. Looking at these > > api > > > changes in Kafka client api without any deprecation warnings, I think > > Kafka > > > does not expect older versions to linger much longer either. > > > > > > On Wed, Feb 8, 2017 at 10:31 AM, Raghu Angadi <[email protected]> > > wrote: > > > > > > > What is the recommended way for users to bundle their app? The fix > > could > > > > as simple as letting the user set version in mvn property > > > > ('kafka.client.version'). > > > > > >
