[VOTE] 0.8.2.1 Candidate 1

38 views
Skip to first unread message

Jun Rao

unread,
Feb 18, 2015, 9:56:17 PM2/18/15
to d...@kafka.apache.org, us...@kafka.apache.org, kafka-...@googlegroups.com
This is the first candidate for release of Apache Kafka 0.8.2.1. This
only fixes one critical issue (KAFKA-1952) in 0.8.2.0.

Release Notes for the 0.8.2.1 release

*** Please download, test and vote by Saturday, Feb 21, 7pm PT

Kafka's KEYS file containing PGP keys we use to sign the release:
http://kafka.apache.org/KEYS in addition to the md5, sha1
and sha2 (SHA256) checksum.

* Release artifacts to be voted upon (source and binary):

* Maven artifacts to be voted upon prior to release:

* scala-doc

* java-doc

* The tag to be voted upon (off the 0.8.2 branch) is the 0.8.2.1 tag

/*******************************************

Thanks,

Jun

Joe Stein

unread,
Feb 21, 2015, 9:04:54 PM2/21/15
to us...@kafka.apache.org, d...@kafka.apache.org, kafka-...@googlegroups.com
Source verified, tests pass, quick start ok.


If the release passes we should update the release notes to include the change from KAFKA-1729 please.

+1 (binding)

~ Joe Stein

On Fri, Feb 20, 2015 at 9:08 PM, ted won <realt...@gmail.com> wrote:
+1

On Friday, February 20, 2015, Guozhang Wang <wang...@gmail.com> wrote:

> +1 binding.
>
> Checked the md5, and quick start.
>
> Some minor comments:
>
> 1. The quickstart section would better include the building step after
> download and before starting server.
>
> 2. There seems to be a bug in Gradle 1.1x with Java 8 causing the "gradle"
> initialization to fail:
>
> ---------
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file '/home/guwang/Workspace/temp/kafka/build.gradle' line: 199
>
> * What went wrong:
> A problem occurred evaluating root project 'kafka'.
> > Could not create task of type 'ScalaDoc'.
> --------------
>
> Downgrading Java to 1.7 resolve this issue.
>
> Guozhang
>
> On Wed, Feb 18, 2015 at 7:56 PM, Connie Yang <cyber...@gmail.com
> <javascript:;>> wrote:
>
> > +1
> > On Feb 18, 2015 7:23 PM, "Matt Narrell" <matt.n...@gmail.com
> <javascript:;>> wrote:
> >
> > > +1
> > >
> > > > On Feb 18, 2015, at 7:56 PM, Jun Rao <j...@confluent.io
> --
> -- Guozhang
>

Jun Rao

unread,
Feb 22, 2015, 11:59:35 AM2/22/15
to Joe Stein, us...@kafka.apache.org, d...@kafka.apache.org, kafka-...@googlegroups.com
We identified at least one more blocker issue KAFKA-1971 during testing. So, we will have to roll another RC for 0.8.2.1.

Thanks,

Jun

--
You received this message because you are subscribed to the Google Groups "kafka-clients" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kafka-client...@googlegroups.com.
To post to this group, send email to kafka-...@googlegroups.com.
Visit this group at http://groups.google.com/group/kafka-clients.
To view this discussion on the web visit https://groups.google.com/d/msgid/kafka-clients/CAA7ooCDvUNQx2B351P3LaOYAejoxR9M_PbzfmWo5-ssgEJ_%2Bpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Joe Stein

unread,
Feb 22, 2015, 5:12:57 PM2/22/15
to Jun Rao, us...@kafka.apache.org, d...@kafka.apache.org, kafka-...@googlegroups.com
Jun, 

Can we also add https://issues.apache.org/jira/browse/KAFKA-1724 to the next RC please? 

Thanks!

~ Joe Stein
- - - - - - - - - - - - - - - - -
  
- - - - - - - - - - - - - - - - - 

Jun Rao

unread,
Feb 23, 2015, 5:50:50 PM2/23/15
to Joe Stein, us...@kafka.apache.org, d...@kafka.apache.org, kafka-...@googlegroups.com
Hi, Joe,

Left a comment on KAFKA-1724. Not sure if it's a true blocker. However, we can probably include it if it can be fixed in the next couple of days.

Thanks,

Jun

Jun Rao

unread,
Feb 24, 2015, 5:33:26 PM2/24/15
to Joe Stein, us...@kafka.apache.org, d...@kafka.apache.org, kafka-...@googlegroups.com
Joe,

It turns out that KAFKA-1724 is already resolved in trunk through another jira. However, the change in that jira is big. Since KAFKA-1724 seems to only happen when there is ZK session timeout or the ZK service is not available, I don't think it's worth fixing the issue in 0.8.2.

Thanks,

Jun
Reply all
Reply to author
Forward
0 new messages