Thanks for everyone who voted. Having community vote of confidence in
bugfix releases is hugely important, especially as we are trying to
support more in-flight versions :)

On Wed, Dec 21, 2016 at 8:49 AM, Ismael Juma <ism...@juma.me.uk> wrote:
> Hi Guozhang,
>
> Thanks for driving this release as it includes a few important fixes. I
> belatedly tested Scala 2.12 binaries using the quickstart,  +1
> (non-binding) from me.
>
> Ismael
>
> On Thu, Dec 15, 2016 at 1:29 PM, Guozhang Wang <wangg...@gmail.com> wrote:
>
>> Hello Kafka users, developers and client-developers,
>>
>> This is the second, and hopefully the last candidate for the release of
>> Apache Kafka 0.10.1.1 before the break. This is a bug fix release and it
>> includes fixes and improvements from 30 JIRAs. See the release notes for
>> more details:
>>
>> http://home.apache.org/~guozhang/kafka-0.10.1.1-rc1/RELEASE_NOTES.html
>>
>> *** Please download, test and vote by Tuesday, 20 December, 8pm 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/~guozhang/kafka-0.10.1.1-rc1/
>>
>> * Maven artifacts to be voted upon:
>> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>>
>> NOTE the artifacts include the ones built from Scala 2.12.1 and Java8,
>> which are treated a pre-alpha artifacts for the Scala community to try and
>> test it out:
>>
>> https://repository.apache.org/content/groups/staging/org/apa
>> che/kafka/kafka_2.12/0.10.1.1/
>>
>> We will formally add the scala 2.12 support in future minor releases.
>>
>>
>> * Javadoc:
>> http://home.apache.org/~guozhang/kafka-0.10.1.1-rc1/javadoc/
>>
>> * Tag to be voted upon (off 0.10.0 branch) is the 0.10.0.1-rc0 tag:
>> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=
>> c3638376708ee6c02dfe4e57747acae0126fa6e7
>>
>>
>> Thanks,
>> Guozhang
>>
>> --
>> -- Guozhang
>>



-- 
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog

Reply via email to