Hi, Nick, Good point. Sorry I forgot to push the latest tag out to the remote repo. Here is the tag that used to publish all binary tar balls: release-0.10.0-rc2
Thanks! -Yi On Tue, May 10, 2016 at 11:24 AM, Nick Quinn <nqu...@objectivity.com> wrote: > Thanks Yi! > > One more question, if I may: I saw that you dropped a 0.10.0 in December > of 2015, but the version in Github is still 0.10.0-rc. Do you guys plan on > an official release of 0.10.0 or are you settling for a simple rc release? > The reason I ask is that it is hard to match the git commits to the release > when there is no official 0.10.0 release. > > Thanks! > Nick > > > -----Original Message----- > From: Yi Pan [mailto:nickpa...@gmail.com] > Sent: Tuesday, May 10, 2016 11:22 AM > To: dev@samza.apache.org > Subject: Re: Kafka dependency > > Hi, Nick, > > We do have plan to update the Kafka dependency in Samza. However, Samza > only uses Kafka client library. We have confirmed that any Kafka 0.8.2 > clients should be supported by Kafka 0.9 brokers. Hence, it should not > block you if you are thinking of upgrading Kafka broker versions (e.g. > LinkedIn has been running with this combination for a long time). The main > reason that we are taking a bit careful path on the upgrading of Kafka > client version is that there are Samza users who are still running Kafka > 0.8.2 broker version and if we force upgrade the client version to 0.9, it > would likely not be supported by a lower version of Kafka broker. > > If you have any specific use case that requires Kafka client version 0.9 > and above, please speak up. We will put into consideration in our upgrade > plan and timeline. > > Thanks a lot! > > -Yi > > On Tue, May 10, 2016 at 10:28 AM, Nick Quinn <nqu...@objectivity.com> > wrote: > > > Hi guys- > > > > > > > > I was wondering why Samza still has a dependency on Kafka 0.8.2. Does > > your development team have any plans to update the Kafka dependency > > version that Samza is using? > > > > Best, > > > > Nick > > > > >
