Thanks Jay! I would like to keep the vote open until the end (Tuesday, March 4th, 6pm PDT) to give anyone voting time to provide feedback on are any other issues to fix prior to RC2.
More inline, some are new topic discussions not for 0.8.1 necessarily but related to release candidates in general. On Mon, Mar 3, 2014 at 12:53 PM, Jay Kreps <jay.kr...@gmail.com> wrote: > Several minor issues: > 1. No enclosing directory in the tgz. That is tar xzf creates the full > contents in the current directory instead of creating a single kafka > directory with all the files. > I saw that and kind of overlooked it when I changed my build script, I should have said something sooner. Lots of changes but yeah this shouldn't be one of them. I will create a JIRA for the gradle patch that will be required so the tgz is like that post build. I will also go back and update the release process wiki as I need to re-order some of my steps to prevent missing the src upload and anything else. I would even say lets check this in as a `bin/release.sh` but let me get something working first (maybe we have a script in 0.8.2 since it worked for 0.8.1).... maybe once I get better with Gradle (working on it) I can add them in as tasks as we go. > 2. SLF4j error: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > I will try to reproduce this and create a JIRA could be related to some other step(s) in the artifact build process. Will keep an eye to make sure it is isn't there for RC2. > 3. Shouldn't we default to build with Scala 2.9 for the binary release? > I think we should default to whatever version has the most broker usage supported in production environments. If the 0.8.1 broker is most run in production with 2.9.3 then I think that is what the project should build against. Is LinkedIn running Scala version 2.9.3 for 0.8.1? One issue I have run into is with plug-in jars for the broker only built on another Scala version than the broker we release (so plugin is for 2.10.3 and broker is 2.8.0). So is having the broker in multiple supported Scala versions as artifacts an option to discuss? It is very easy to-do during release process. I can stamp out test environments for each at least for consistent builds. Also, Scala 2.11 will be out soon too and that could coincide then for the 0.8.2 (or 0.8.1.1 release as going multiple builds means more maintenance but not in a bad way imho)? 4. I think the JIRAs in the release notes could be better categorized as > bug/improvement/feature, I took a pass at that. thnx, if you haven't I will create a JIRA for this when I create the others later tonight/tomorrow. 5. I think we might want to increase the default num.io.threads from 2 to > 4. This is not a blocker. I just noticed that 2 is too few if you have more > than 2 disks, and most people probably won't tune this. > I will create a JIRA > > -Jay > > > On Fri, Feb 28, 2014 at 6:26 AM, Joe Stein <joe.st...@stealth.ly> wrote: > > > This is the first candidate for release of Apache Kafka 0.8.1. > > > > Release Notes for the 0.8.1 release > > > > > http://people.apache.org/~joestein/kafka-0.8.1-candidate1/RELEASE_NOTES.html > > > > *** Please download, test and vote by Tuesday, March 4th, 6pm PDT > > > > Kafka's KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/kafka/KEYS in addition to the md5, sha1 > > and > > sha2 (SHA256) checksum > > > > * Release artifacts to be voted upon (source and binary): > > http://people.apache.org/~joestein/kafka-0.8.1-candidate1/ > > > > * Maven artifacts to be voted upon prior to release: > > https://repository.apache.org/content/groups/staging/ > > > > * The tag to be voted upon (off the 0.8.1 branch) is the 0.8.1 tag > > > > > https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=0c9f03fd7a6cae909c429a25ffb4624a7fe507ff > > > > /******************************************* > > Joe Stein > > Founder, Principal Consultant > > Big Data Open Source Security LLC > > http://www.stealth.ly > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > ********************************************/ > > >
