Michael, I am rolling out a new RC right now, stay tuned.
Guozhang On Thu, Dec 15, 2016 at 2:34 AM, Michael Pearce <michael.pea...@ig.com> wrote: > Is there any update on this, when do we expect and RC1 for vote? > > We see KAFKA-4497 is marked Resolved. > > Cheers > Mike > > On 13/12/2016, 00:59, "Guozhang Wang" <wangg...@gmail.com> wrote: > > I see. Currently the upload command has not included the 2.12 version > yet, > I will manually do that in the next RC. > > Guozhang > > On Mon, Dec 12, 2016 at 4:47 PM, Bernard Leach < > leac...@bouncycastle.org> > wrote: > > > I found those ones but was hoping to see them in > > https://repository.apache.org/content/groups/staging/org/ > apache/kafka/ < > > https://repository.apache.org/content/groups/staging/org/ > apache/kafka/> > > so we can just point the maven build there for testing. > > > > > On 13 Dec 2016, at 11:38, Guozhang Wang <wangg...@gmail.com> > wrote: > > > > > > @Bernard > > > > > > You should be able to find the artifacts in the staging RC > repository I > > > listed above, named as "kafka_2.12-0.10.1.1.tgz > > > <http://home.apache.org/~guozhang/kafka-0.10.1.1-rc0/ > > kafka_2.12-0.10.1.1.tgz> > > > ". > > > > > > @Everyone > > > > > > Since KAFKA-4497 is a critical issue, that anyone using compaction > with > > > compressed message on server logs can possibly hit it, I'm going to > > create > > > a new RC after it is merged (presumably soon). > > > > > > If you discover any new problems in the meantime, let me know on > this > > > thread. > > > > > > > > > Guozhang > > > > > > > > > On Mon, Dec 12, 2016 at 2:51 PM, Ismael Juma <ism...@juma.me.uk> > wrote: > > > > > >> Yes, it would be good to include that (that's why I set the fix > version > > to > > >> 0.10.1.1 a couple of days ago). > > >> > > >> Ismael > > >> > > >> On Mon, Dec 12, 2016 at 3:47 PM, Moczarski, Swen < > > >> smoczar...@ebay-kleinanzeigen.de> wrote: > > >> > > >>> -0 (non-binding) > > >>> > > >>> Would it make sense to include https://issues.apache.org/ > > >>> jira/browse/KAFKA-4497 ? The issue sounds quite critical and a > patch > > for > > >>> 0.10.1.1 seems to be available. > > >>> > > >>> On 2016-12-07 23:46 (+0100), Guozhang Wang <w...@gmail.com > <mailto: > > w...@ > > >>> gmail.com>> wrote: > > >>>> Hello Kafka users, developers and client-developers,> > > >>>> > > >>>> This is the first candidate for the release of Apache Kafka > 0.10.1.1. > > >>> This is> > > >>>> a bug fix release and it includes fixes and improvements from 27 > > JIRAs. > > >>> See> > > >>>> the release notes for more details:> > > >>>> > > >>>> http://home.apache.org/~guozhang/kafka-0.10.1.1-rc0/ > > RELEASE_NOTES.html > > >>> > > >>>> > > >>>> *** Please download, test and vote by Monday, 13 December, 8am > 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-rc0/> > > >>>> > > >>>> * Maven artifacts to be voted upon:> > > >>>> https://repository.apache.org/content/groups/staging/org/ > > apache/kafka/ > > >>> > > >>>> > > >>>> * Javadoc:> > > >>>> http://home.apache.org/~guozhang/kafka-0.10.1.1-rc0/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= > > >>> 8b77507083fdd427ce81021228e7e346da0d814c> > > >>>> > > >>>> > > >>>> Thanks,> > > >>>> Guozhang> > > >>>> > > >>> > > >> > > > > > > > > > > > > -- > > > -- Guozhang > > > > > > > -- > -- Guozhang > > > The information contained in this email is strictly confidential and for > the use of the addressee only, unless otherwise indicated. If you are not > the intended recipient, please do not read, copy, use or disclose to others > this message or any attachment. Please also notify the sender by replying > to this email or by telephone (+44(020 7896 0011) and then delete the email > and any copies of it. Opinions, conclusion (etc) that do not relate to the > official business of this company shall be understood as neither given nor > endorsed by it. IG is a trading name of IG Markets Limited (a company > registered in England and Wales, company number 04008957) and IG Index > Limited (a company registered in England and Wales, company number > 01190902). Registered address at Cannon Bridge House, 25 Dowgate Hill, > London EC4R 2YA. Both IG Markets Limited (register number 195355) and IG > Index Limited (register number 114059) are authorised and regulated by the > Financial Conduct Authority. > -- -- Guozhang
