Re: [RESULT] [VOTE] 2.3.0 RC3

Thanks for the hard work Colin, and everyone else who helped get this out! On Mon, Jun 24, 2019 at 1:38 PM Colin McCabe wrote: > Hi all, > > This vote passes with 6 +1 votes (3 of which are binding) and no 0 or -1 > votes. Thanks to everyone who voted. > > +1 votes > PMC Members: > * Ismael Jum

[RESULT] [VOTE] 2.3.0 RC3

Hi all, This vote passes with 6 +1 votes (3 of which are binding) and no 0 or -1 votes. Thanks to everyone who voted. +1 votes PMC Members: * Ismael Juma * Guozhang Wang * Gwen Shapira Community: * Kamal Chandraprakash * Jakub Scholz * Mickael Maison 0 votes * No votes -1 votes * No votes V

Re: [VOTE] 2.3.0 RC3

Thanks Colin for making a new RC for KAFKA-8564. +1 (non binding) I checked signatures and ran quickstart on the 2.12 binary On Mon, Jun 24, 2019 at 6:03 AM Gwen Shapira wrote: > > +1 (binding) > Verified signatures, verified good build on jenkins, built from > sources anyway and ran quickstart o

Re: [VOTE] 2.3.0 RC3

+1 (binding) Verified signatures, verified good build on jenkins, built from sources anyway and ran quickstart on the 2.11 binary. Looks good! On Sun, Jun 23, 2019 at 3:06 PM Jakub Scholz wrote: > > +1 (non-binding). I used the binaries and run some of my tests against them. > > On Thu, Jun 20,

Re: [VOTE] 2.3.0 RC3

+1 (non-binding). I used the binaries and run some of my tests against them. On Thu, Jun 20, 2019 at 12:03 AM Colin McCabe wrote: > Hi all, > > We discovered some problems with the second release candidate (RC2) of > 2.3.0. Specifically, KAFKA-8564. I've created a new RC which includes the > f

Re: [VOTE] 2.3.0 RC3

Hi Colin, Thanks for the new RC, +1 (binding). Verified the javadoc, maven repo, and ran unit tests on 2.12 binary. Guozhang On Fri, Jun 21, 2019 at 1:23 PM Colin McCabe wrote: > Hi Ismael, > > Good catch. This should be fixed now. > > It seems that if the previously staged Sonatype stagin

Re: [VOTE] 2.3.0 RC3

Hi Ismael, Good catch. This should be fixed now. It seems that if the previously staged Sonatype staging repositories (from the previous RCs) are not dropped as part of the release process, the new ones don't get exposed. Maybe we should document this somewhere (it was a bit of a surprise wh

Re: [VOTE] 2.3.0 RC3

Hi Colin, One more thing: the Maven repo was not updated, it seems. Can you fix that? Ismael On Fri, Jun 21, 2019 at 8:23 AM Ismael Juma wrote: > Hi Colin, > > Thanks, +1 (binding). > > I verified the quickstart and signatures for the source and kafka 2.12 > artifacts with Java 11. One note is

Re: [VOTE] 2.3.0 RC3

Hi Colin, Thanks, +1 (binding). I verified the quickstart and signatures for the source and kafka 2.12 artifacts with Java 11. One note is that we need to complete the upgrade section for 2.3.0 before we announce the release. No new RC is needed, we just have to have it on the website. Ismael O

Re: [VOTE] 2.3.0 RC3

+1 (non-binding) * Ran unit and integration test on 2.11 and 2.12 * Verified quick start * Ran internal apps on the 3 node cluster On Thu, Jun 20, 2019 at 3:33 AM Colin McCabe wrote: > Hi all, > > We discovered some problems with the second release candidate (RC2) of > 2.3.0. Specifically, KAF

[VOTE] 2.3.0 RC3

Hi all, We discovered some problems with the second release candidate (RC2) of 2.3.0. Specifically, KAFKA-8564. I've created a new RC which includes the fix for this issue. Check out the release notes for the 2.3.0 release here: https://home.apache.org/~cmccabe/kafka-2.3.0-rc3/RELEASE_NOTES.h