Hi Jason,
I see in the release notes that this issue seems to be fixed, but is
marked as 'duplicate'
https://issues.apache.org/jira/browse/KAFKA-156

Maybe you can consider removing this kind of un-fixed issues from the
release notes.
In my case I'm waiting for that fix and I 'was' very happy to see in
resolved, but this is not the case

Thank you

-- Enrico



2016-10-05 1:13 GMT+02:00 Jason Gustafson <ja...@confluent.io>:
> One clarification: this is a minor release, not a major one.
>
> -Jason
>
> On Tue, Oct 4, 2016 at 4:01 PM, Jason Gustafson <ja...@confluent.io> wrote:
>
>> Hello Kafka users, developers and client-developers,
>>
>> This is the first candidate for release of Apache Kafka 0.10.1.0. This is
>> a major release that includes great new features including throttled
>> replication, secure quotas, time-based log searching, and queryable state
>> for Kafka Streams. A full list of the content can be found here:
>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. Since
>> this is a major release, we will give people more time to try it out and
>> give feedback.
>>
>> Release notes for the 0.10.1.0 release:
>> http://home.apache.org/~jgus/kafka-0.10.1.0-rc0/RELEASE_NOTES.html
>>
>> *** Please download, test and vote by Monday, Oct 10, 9am PT
>>
>> Kafka's KEYS file containing PGP keys we use to sign the release:
>> http://kafka.apache.org/KEYS
>>
>> * Release artifacts to be voted upon (source and binary):
>> http://home.apache.org/~jgus/kafka-0.10.1.0-rc0/
>>
>> * Maven artifacts to be voted upon:
>> https://repository.apache.org/content/groups/staging/
>>
>> * Javadoc:
>> http://home.apache.org/~jgus/kafka-0.10.1.0-rc0/javadoc/
>>
>> * Tag to be voted upon (off 0.10.1 branch) is the 0.10.1.0 tag:
>> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=
>> b86130bad1a1a4a3d1dbe5c486977e6968b3ebc6
>>
>> * Documentation:
>> http://kafka.apache.org/0101/documentation.html
>>
>> * Protocol:
>> http://kafka.apache.org/0101/protocol.html
>>
>> Note that integration/system testing on Jenkins has been a major problem
>> this release cycle. In order to validate this RC, we need to get these
>> tests stable again. Any help we can get from the community will be greatly
>> appreciated.
>>
>> Thanks,
>>
>> Jason
>>

Reply via email to