Hello,

This is the first candidate for the second incubator release for
Apache Kafka, version 0.7.1-incubating.

This release fixes the following issues
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/RELEASE-NOTES.html

*** Please download, test and vote by Monday June, 18th, 12pm PDT

Release artifacts:
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/

The tag to be voted upon (off the 0.7.1 branch):
https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-1

Kafka's KEYS file containing PGP keys we use to sign the release:
http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

On 14 June 2012 17:34, Joe Stein <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This is the first candidate for the second incubator release for
> Apache Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/RELEASE-NOTES.html
>
> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/
>
> The tag to be voted upon (off the 0.7.1 branch):
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-1

NOTICE says:

Copyright 2011

> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */

Vote cancelled

I will roll RC2 with a fix for this issue (
https://issues.apache.org/jira/browse/KAFKA-365) within it

thanks!

On Thu, Jun 14, 2012 at 12:45 PM, sebb <[EMAIL PROTECTED]> wrote:

> On 14 June 2012 17:34, Joe Stein <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > This is the first candidate for the second incubator release for
> > Apache Kafka, version 0.7.1-incubating.
> >
> > This release fixes the following issues
> >
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/RELEASE-NOTES.html
> >
> > *** Please download, test and vote by Monday June, 18th, 12pm PDT
> >
> > Release artifacts:
> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/
> >
> > The tag to be voted upon (off the 0.7.1 branch):
> >
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-1
>
> NOTICE says:
>
> Copyright 2011
>
>
>
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
> >
> > /*
> > Joe Stein
> > http://www.linkedin.com/in/charmalloc
> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > */
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

Hello,

This is the second candidate for the second incubator release for Apache
Kafka, version 0.7.1-incubating.

This release fixes the following issues
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html

RC2 fixes the issue identified in RC1 =>
https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
to 2012

*** Please download, test and vote by Monday June, 18th, 12pm PDT

Release artifacts:
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/

The tag to be voted upon (off the 0.7.1 branch):
https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2

Kafka's KEYS file containing PGP keys we use to sign the release:
http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

+1

Ran quick start, unit tests and rat tests.

Thanks,

Jun

On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Hello,
>
> This is the second candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
>
> RC2 fixes the issue identified in RC1 =>
> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
> to 2012
>
> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
>
> The tag to be voted upon (off the 0.7.1 branch):
>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

Can other people (including mentors) help vote on this release?

Thanks,

Jun

On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Hello,
>
> This is the second candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
>
> RC2 fixes the issue identified in RC1 =>
> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
> to 2012
>
> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
>
> The tag to be voted upon (off the 0.7.1 branch):
>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

Any other voters?

Thanks,

Jun

On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Hello,
>
> This is the second candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
>
> RC2 fixes the issue identified in RC1 =>
> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
> to 2012
>
> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
>
> The tag to be voted upon (off the 0.7.1 branch):
>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

I would like to give this a look today - I can vote by tomorrow.

Thanks,

Joel

On Mon, Jun 18, 2012 at 10:14 AM, Jun Rao <[EMAIL PROTECTED]> wrote:

> Any other voters?
>
> Thanks,
>
> Jun
>
> On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > This is the second candidate for the second incubator release for Apache
> > Kafka, version 0.7.1-incubating.
> >
> > This release fixes the following issues
> >
> >
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
> >
> > RC2 fixes the issue identified in RC1 =>
> > https://issues.apache.org/jira/browse/KAFKA-365 change copyright in
> NOTICE
> > to 2012
> >
> > *** Please download, test and vote by Monday June, 18th, 12pm PDT
> >
> > Release artifacts:
> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
> >
> > The tag to be voted upon (off the 0.7.1 branch):
> >
> >
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
> >
> > /*
> > Joe Stein
> > http://www.linkedin.com/in/charmalloc
> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > */
> >
>

Things that I've noted:

I don't see a checksum for your release in http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ -- your release manager will need to generate a checksum for the release.

It would be nice if your archive extracted into an apache-kafka-0.7.1-incubating directory (or similar name rather than .), but that's minor.

I see the following binary files in your source distribution:

./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll
./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar
./contrib/hadoop-consumer/lib/piggybank.jar
./contrib/hadoop-producer/lib/pig-0.8.0-core.jar
./contrib/hadoop-producer/lib/piggybank.jar
./lib/sbt-launch.jar

If I understand correctly, this does not meet a definition of an open source release (which is what an apache release is…). It looks like this is how your last release was packaged, also… I don't know if this is a blocking issue (for an incubator release), but I think you need to work on resolving this (i.e. remove binaries from your source)…

IIUC, your LICENSE/NOTICE files are documenting your "source" (including the above jars). Do you document the LICENSE/NOTICE of your binaries? I built kafka and see that a number jars are pulled in… I have no idea what the LICENSING for these artifacts is… and whether or not they conform to ASF standards (I did not review them all). Your project needs to document them.

FYI, I couldn't figure out from the documentation how to start a server after I built kafka.

--kevan

On Jun 18, 2012, at 1:14 PM, Jun Rao wrote:

> Any other voters?
>
> Thanks,
>
> Jun
>
> On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> This is the second candidate for the second incubator release for Apache
>> Kafka, version 0.7.1-incubating.
>>
>> This release fixes the following issues
>>
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
>>
>> RC2 fixes the issue identified in RC1 =>
>> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
>> to 2012
>>
>> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>>
>> Release artifacts:
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
>>
>> The tag to be voted upon (off the 0.7.1 branch):
>>
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
>>
>> Kafka's KEYS file containing PGP keys we use to sign the release:
>> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>>
>> /*
>> Joe Stein
>> http://www.linkedin.com/in/charmalloc
>> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
>> */
>>

I uploaded a md5 checksum
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ to
go along with the detached signature that was generated already

starting the kafka server is in the quick start
http://incubator.apache.org/kafka/quickstart.html

looking at Cassandra and Hadoop source distributions both have jars in them
too, so not sure the issue you are raising others might have a better
understanding or I am missing something you are trying to point out

I would like to keep the RC2 voting open for another few days to see if
this release passes (as folks have not had time to review) or we can get to
what issues we need to have resolved that can be done for RC3 for a new
vote either with objective to getting 0.7.1 released.

current votes:

+1 [1] +0 [0] -1 [0] from the PPMC

and

+1 [0] +0 [0] -1 [0] from the IPMC

please let me know if there is something different we want or should have
been doing here or that I can be or should be doing differently.

thanks!

On Mon, Jun 18, 2012 at 4:53 PM, Kevan Miller <[EMAIL PROTECTED]>wrote:

> Things that I've noted:
>
> I don't see a checksum for your release in
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ --
> your release manager will need to generate a checksum for the release.
>
> It would be nice if your archive extracted into an
> apache-kafka-0.7.1-incubating directory (or similar name rather than .),
> but that's minor.
>
> I see the following binary files in your source distribution:
>
> ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll
> ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar
> ./contrib/hadoop-consumer/lib/piggybank.jar
> ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar
> ./contrib/hadoop-producer/lib/piggybank.jar
> ./lib/sbt-launch.jar
>
> If I understand correctly, this does not meet a definition of an open
> source release (which is what an apache release is…). It looks like this is
> how your last release was packaged, also… I don't know if this is a
> blocking issue (for an incubator release), but I think you need to work on
> resolving this (i.e. remove binaries from your source)…
>
> IIUC, your LICENSE/NOTICE files are documenting your "source" (including
> the above jars). Do you document the LICENSE/NOTICE of your binaries? I
> built kafka and see that a number jars are pulled in… I have no idea what
> the LICENSING for these artifacts is… and whether or not they conform to
> ASF standards (I did not review them all). Your project needs to document
> them.
>
> FYI, I couldn't figure out from the documentation how to start a server
> after I built kafka.
>
> --kevan
>
> On Jun 18, 2012, at 1:14 PM, Jun Rao wrote:
>
> > Any other voters?
> >
> > Thanks,
> >
> > Jun
> >
> > On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
> >
> >> Hello,
> >>
> >> This is the second candidate for the second incubator release for Apache
> >> Kafka, version 0.7.1-incubating.
> >>
> >> This release fixes the following issues
> >>
> >>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
> >>
> >> RC2 fixes the issue identified in RC1 =>
> >> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in
> NOTICE
> >> to 2012
> >>
> >> *** Please download, test and vote by Monday June, 18th, 12pm PDT
> >>
> >> Release artifacts:
> >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
> >>
> >> The tag to be voted upon (off the 0.7.1 branch):
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
> >>
> >> Kafka's KEYS file containing PGP keys we use to sign the release:
> >> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
> >>
> >> /*
> >> Joe Stein
> >> http://www.linkedin.com/in/charmalloc
> >> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> >> */
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

Kevin,

Thanks for the comments. Just want to clarify on your points on
LICENSE/NOTICE. Our LICENSE/NOTICE covers all jars included in the source,
not those pulled in during building. We had a long discussion during our
1st release and in the end, we have reached the conclusion that we don't
have to document LICENSE/NOTICE for jars not included in the source (since
we are just doing a source release). Please correct me if you think this is
blocking the release. We have to include a small number of jars in the
source because there is no easy way to pull them in automatically.

Thanks,

Jun

On Mon, Jun 18, 2012 at 1:53 PM, Kevan Miller <[EMAIL PROTECTED]>wrote:

> Things that I've noted:
>
> I don't see a checksum for your release in
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ --
> your release manager will need to generate a checksum for the release.
>
> It would be nice if your archive extracted into an
> apache-kafka-0.7.1-incubating directory (or similar name rather than .),
> but that's minor.
>
> I see the following binary files in your source distribution:
>
> ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll
> ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar
> ./contrib/hadoop-consumer/lib/piggybank.jar
> ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar
> ./contrib/hadoop-producer/lib/piggybank.jar
> ./lib/sbt-launch.jar
>
> If I understand correctly, this does not meet a definition of an open
> source release (which is what an apache release is…). It looks like this is
> how your last release was packaged, also… I don't know if this is a
> blocking issue (for an incubator release), but I think you need to work on
> resolving this (i.e. remove binaries from your source)…
>
> IIUC, your LICENSE/NOTICE files are documenting your "source" (including
> the above jars). Do you document the LICENSE/NOTICE of your binaries? I
> built kafka and see that a number jars are pulled in… I have no idea what
> the LICENSING for these artifacts is… and whether or not they conform to
> ASF standards (I did not review them all). Your project needs to document
> them.
>
> FYI, I couldn't figure out from the documentation how to start a server
> after I built kafka.
>
> --kevan
>
> On Jun 18, 2012, at 1:14 PM, Jun Rao wrote:
>
> > Any other voters?
> >
> > Thanks,
> >
> > Jun
> >
> > On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
> >
> >> Hello,
> >>
> >> This is the second candidate for the second incubator release for Apache
> >> Kafka, version 0.7.1-incubating.
> >>
> >> This release fixes the following issues
> >>
> >>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
> >>
> >> RC2 fixes the issue identified in RC1 =>
> >> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in
> NOTICE
> >> to 2012
> >>
> >> *** Please download, test and vote by Monday June, 18th, 12pm PDT
> >>
> >> Release artifacts:
> >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
> >>
> >> The tag to be voted upon (off the 0.7.1 branch):
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
> >>
> >> Kafka's KEYS file containing PGP keys we use to sign the release:
> >> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
> >>
> >> /*
> >> Joe Stein
> >> http://www.linkedin.com/in/charmalloc
> >> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> >> */
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

I don't think we should release as is.

- project.version is set to 0.7.0
- Have not released since the general@ threads highlighted the included
jars problem.  Thanks for pointing that out Kevan.

(The unit test also don't pass for me but that could easily be a local
issue, I'll try to get a branch specific jenkins build going.)

On 06/14/2012 02:42 PM, Joe Stein wrote:
> Hello,
>
> This is the second candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
>
> RC2 fixes the issue identified in RC1 =>
> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE
> to 2012
>
> *** Please download, test and vote by Monday June, 18th, 12pm PDT
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
>
> The tag to be voted upon (off the 0.7.1 branch):
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

yup, will do.  I will also change the version to 0.7.1 in the
build.properties after I commit kafka-366

On Tue, Jun 19, 2012 at 12:50 AM, Jun Rao <[EMAIL PROTECTED]> wrote:

> ---------- Forwarded message ----------
> From: Jun Rao <[EMAIL PROTECTED]>
> Date: Mon, Jun 18, 2012 at 9:49 PM
> Subject: Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)
> To: [EMAIL PROTECTED]
>
>
> Joe,
>
> It looks like that we need to create a new RC. Could you pick up kafka-366?
> It just adds a new jmx.
>
> Thanks,
>
> Jun
>
> On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > This is the second candidate for the second incubator release for Apache
> > Kafka, version 0.7.1-incubating.
> >
> > This release fixes the following issues
> >
> >
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html
> >
> > RC2 fixes the issue identified in RC1 =>
> > https://issues.apache.org/jira/browse/KAFKA-365 change copyright in
> NOTICE
> > to 2012
> >
> > *** Please download, test and vote by Monday June, 18th, 12pm PDT
> >
> > Release artifacts:
> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/
> >
> > The tag to be voted upon (off the 0.7.1 branch):
> >
> >
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS
> >
> > /*
> > Joe Stein
> > http://www.linkedin.com/in/charmalloc
> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > */
> >
>

--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

Hello,

This is the third candidate for the second incubator release for Apache
Kafka, version 0.7.1-incubating.

This release fixes the following issues
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html

Release artifacts:
http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3

The tag to be voted upon (off the 0.7.1 branch):
https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/

Kafka's KEYS file containing PGP keys we use to sign the release:
http://svn.apache.org/repos/asf/incubator/kafka/KEYS

The vote will be open for 72 hours (longer if needed).

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:

> Hello,
>
> This is the third candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>
> The tag to be voted upon (off the 0.7.1 branch):
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> The vote will be open for 72 hours (longer if needed).
I need help checking these jars.  What I recommend is that we update NOTICE in trunk as we attribute licenses to the jars below.  This way we still vet the jars, update the NOTICE/LICENSE file in trunk for the next release, and not force Joe to cut a new release to include the updated NOTICE/LICENSE file.

This will make subsequent releases go much easier.

BTW, the keys and signatures are fine.  Tests pass.

(linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
./contrib/hadoop-consumer/lib/piggybank.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-api-2.1-6.1.14.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/kfs-0.3.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-generator-2.2.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/pig-0.8.0.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/qdox-1.10.1.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/servlet-api-2.5-6.1.14.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/slf4j-api-1.5.11.jar
./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/xmlenc-0.52.jar
./contrib/hadoop-consumer/target/scala_2.8.0/hadoop-consumer_2.8.0-0.7.1.jar
./contrib/hadoop-producer/lib/piggybank.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/avro-1.4.0.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-collections-3.2.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.5.5.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.5.5.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-6.1.22.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.22.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
./contrib/hadoop-producer/lib_managed/scala_2.8.0/compil

Did these dependencies change between 0.7.0 and 0.7.1? -C

On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
>
> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>
>> Hello,
>>
>> This is the third candidate for the second incubator release for Apache
>> Kafka, version 0.7.1-incubating.
>>
>> This release fixes the following issues
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>>
>> Release artifacts:
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>>
>> The tag to be voted upon (off the 0.7.1 branch):
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>>
>> Kafka's KEYS file containing PGP keys we use to sign the release:
>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>
>> The vote will be open for 72 hours (longer if needed).
>
>
> I need help checking these jars.  What I recommend is that we update NOTICE in trunk as we attribute licenses to the jars below.  This way we still vet the jars, update the NOTICE/LICENSE file in trunk for the next release, and not force Joe to cut a new release to include the updated NOTICE/LICENSE file.
>
> This will make subsequent releases go much easier.
>
> BTW, the keys and signatures are fine.  Tests pass.
>
> (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
> ./contrib/hadoop-consumer/lib/piggybank.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-api-2.1-6.1.14.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/kfs-0.3.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-generator-2.2.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/pig-0.8.0.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/qdox-1.10.1.jar
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/servlet-api-2.5-6.1.14.jar

1) snappy-java-1.0.4.1.jar is required when setting Snappy as a compression
codec which is pulled from maven from ./sbt update and is Apache License
2.0 http://code.google.com/p/snappy-java/
2) ZooKeeper client jar upgraded from 3.3.3 to 3.3.4

On Thu, Jun 21, 2012 at 2:32 PM, Chris Douglas <[EMAIL PROTECTED]> wrote:

> Did these dependencies change between 0.7.0 and 0.7.1? -C
>
> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]>
> wrote:
> >
> > On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
> >
> >> Hello,
> >>
> >> This is the third candidate for the second incubator release for Apache
> >> Kafka, version 0.7.1-incubating.
> >>
> >> This release fixes the following issues
> >>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
> >>
> >> Release artifacts:
> >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
> >>
> >> The tag to be voted upon (off the 0.7.1 branch):
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
> >>
> >> Kafka's KEYS file containing PGP keys we use to sign the release:
> >> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
> >>
> >> The vote will be open for 72 hours (longer if needed).
> >
> >
> > I need help checking these jars.  What I recommend is that we update
> NOTICE in trunk as we attribute licenses to the jars below.  This way we
> still vet the jars, update the NOTICE/LICENSE file in trunk for the next
> release, and not force Joe to cut a new release to include the updated
> NOTICE/LICENSE file.
> >
> > This will make subsequent releases go much easier.
> >
> > BTW, the keys and signatures are fine.  Tests pass.
> >
> > (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
> > ./contrib/hadoop-consumer/lib/piggybank.jar
> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-api-2.1-6.1.14.jar
> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/kfs-0.3.jar
> >
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar
/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

Not sure. It's simple enough to check the email archives for my last plea.

With that said, I was hoping we could kill two birds with one stone.
Regards,
Alan

 
On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:

> Did these dependencies change between 0.7.0 and 0.7.1? -C
>
> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
>>
>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>>
>>> Hello,
>>>
>>> This is the third candidate for the second incubator release for Apache
>>> Kafka, version 0.7.1-incubating.
>>>
>>> This release fixes the following issues
>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>>>
>>> Release artifacts:
>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>>>
>>> The tag to be voted upon (off the 0.7.1 branch):
>>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>>>
>>> Kafka's KEYS file containing PGP keys we use to sign the release:
>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>>
>>> The vote will be open for 72 hours (longer if needed).
>>
>>
>> I need help checking these jars.  What I recommend is that we update NOTICE in trunk as we attribute licenses to the jars below.  This way we still vet the jars, update the NOTICE/LICENSE file in trunk for the next release, and not force Joe to cut a new release to include the updated NOTICE/LICENSE file.
>>
>> This will make subsequent releases go much easier.
>>
>> BTW, the keys and signatures are fine.  Tests pass.
>>
>> (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
>> ./contrib/hadoop-consumer/lib/piggybank.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-api-2.1-6.1.14.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/kfs-0.3.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar

Great. We're not distributing the Snappy codec, so- according to the
reasoning of board@, legal@, and the IPMC on the 0.7.0 release- the
NOTICE and LICENSE files do not require updates. We're not starting
from first principles at every release.

I'm +1 on RC3. The LICENSE/NOTICE files contain the necessary
citations for Nunit and sbt, the checksum and signature match, the
DISCLAIMER is correct. -C

On Thu, Jun 21, 2012 at 12:13 PM, Joe Stein <[EMAIL PROTECTED]> wrote:
> 1) snappy-java-1.0.4.1.jar is required when setting Snappy as a compression
> codec which is pulled from maven from ./sbt update and is Apache License
> 2.0 http://code.google.com/p/snappy-java/
> 2) ZooKeeper client jar upgraded from 3.3.3 to 3.3.4
>
> On Thu, Jun 21, 2012 at 2:32 PM, Chris Douglas <[EMAIL PROTECTED]> wrote:
>
>> Did these dependencies change between 0.7.0 and 0.7.1? -C
>>
>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]>
>> wrote:
>> >
>> > On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>> >
>> >> Hello,
>> >>
>> >> This is the third candidate for the second incubator release for Apache
>> >> Kafka, version 0.7.1-incubating.
>> >>
>> >> This release fixes the following issues
>> >>
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>> >>
>> >> Release artifacts:
>> >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>> >>
>> >> The tag to be voted upon (off the 0.7.1 branch):
>> >>
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>> >>
>> >> Kafka's KEYS file containing PGP keys we use to sign the release:
>> >> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>> >>
>> >> The vote will be open for 72 hours (longer if needed).
>> >
>> >
>> > I need help checking these jars.  What I recommend is that we update
>> NOTICE in trunk as we attribute licenses to the jars below.  This way we
>> still vet the jars, update the NOTICE/LICENSE file in trunk for the next
>> release, and not force Joe to cut a new release to include the updated
>> NOTICE/LICENSE file.
>> >
>> > This will make subsequent releases go much easier.
>> >
>> > BTW, the keys and signatures are fine.  Tests pass.
>> >
>> > (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
>> > ./contrib/hadoop-consumer/lib/piggybank.jar
>> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
>> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
>> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
>> > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
>> >
>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar

+1 on the release.

Run quickstart and unit tests. All good.

Thanks,

Jun

On Wed, Jun 20, 2012 at 9:19 AM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Hello,
>
> This is the third candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
> This release fixes the following issues
>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>
> Release artifacts:
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>
> The tag to be voted upon (off the 0.7.1 branch):
>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> The vote will be open for 72 hours (longer if needed).
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

It's the PPMC's job to vet these dependencies, not the mentors.  I already did this once after no one answered my request for help during the 0.7.0 vote.  Someone from the Kafka PPMC needs to step up.  My vote will depend on the outcome of this check.

BTW, there's a number of duplicate jars.  Not sure if that will be a problem.
Regards,
Alan

 
On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:

> Not sure. It's simple enough to check the email archives for my last plea.
>
> With that said, I was hoping we could kill two birds with one stone.
>
>
> Regards,
> Alan
>
>
> On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
>
>> Did these dependencies change between 0.7.0 and 0.7.1? -C
>>
>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
>>>
>>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>>>
>>>> Hello,
>>>>
>>>> This is the third candidate for the second incubator release for Apache
>>>> Kafka, version 0.7.1-incubating.
>>>>
>>>> This release fixes the following issues
>>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>>>>
>>>> Release artifacts:
>>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>>>>
>>>> The tag to be voted upon (off the 0.7.1 branch):
>>>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>>>>
>>>> Kafka's KEYS file containing PGP keys we use to sign the release:
>>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>>>
>>>> The vote will be open for 72 hours (longer if needed).
>>>
>>>
>>> I need help checking these jars.  What I recommend is that we update NOTICE in trunk as we attribute licenses to the jars below.  This way we still vet the jars, update the NOTICE/LICENSE file in trunk for the next release, and not force Joe to cut a new release to include the updated NOTICE/LICENSE file.
>>>
>>> This will make subsequent releases go much easier.
>>>
>>> BTW, the keys and signatures are fine.  Tests pass.
>>>
>>> (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name "*.jar"
>>> ./contrib/hadoop-consumer/lib/piggybank.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar
>>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar

Alan,

I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades, the
only added jar in 0.7.1 is the following.
./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar

Snappy is on Apache License 2.0. So, our licenses should be covered.

Thanks,

Jun
On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:

> It's the PPMC's job to vet these dependencies, not the mentors.  I already
> did this once after no one answered my request for help during the 0.7.0
> vote.  Someone from the Kafka PPMC needs to step up.  My vote will depend
> on the outcome of this check.
>
> BTW, there's a number of duplicate jars.  Not sure if that will be a
> problem.
>
>
> Regards,
> Alan
>
>
> On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:
>
> > Not sure. It's simple enough to check the email archives for my last
> plea.
> >
> > With that said, I was hoping we could kill two birds with one stone.
> >
> >
> > Regards,
> > Alan
> >
> >
> > On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
> >
> >> Did these dependencies change between 0.7.0 and 0.7.1? -C
> >>
> >> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <[EMAIL PROTECTED]>
> wrote:
> >>>
> >>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
> >>>
> >>>> Hello,
> >>>>
> >>>> This is the third candidate for the second incubator release for
> Apache
> >>>> Kafka, version 0.7.1-incubating.
> >>>>
> >>>> This release fixes the following issues
> >>>>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
> >>>>
> >>>> Release artifacts:
> >>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
> >>>>
> >>>> The tag to be voted upon (off the 0.7.1 branch):
> >>>>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
> >>>>
> >>>> Kafka's KEYS file containing PGP keys we use to sign the release:
> >>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
> >>>>
> >>>> The vote will be open for 72 hours (longer if needed).
> >>>
> >>>
> >>> I need help checking these jars.  What I recommend is that we update
> NOTICE in trunk as we attribute licenses to the jars below.  This way we
> still vet the jars, update the NOTICE/LICENSE file in trunk for the next
> release, and not force Joe to cut a new release to include the updated
> NOTICE/LICENSE file.
> >>>
> >>> This will make subsequent releases go much easier.
> >>>
> >>> BTW, the keys and signatures are fine.  Tests pass.
> >>>
> >>> (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name
> "*.jar"
> >>> ./contrib/hadoop-consumer/lib/piggybank.jar
> >>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
> >>> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar
> >>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar

Alan,

Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
Extract *.jar, sort them, and compare. I reached the same conclusion as
Joe: the only new jar is snappy. Other jar differences are all due to jar
upgrades (are you referring to those?). Could you list any other completely
new jars that are not included in 0,7.0 already?

Thanks,

Jun
On Fri, Jun 22, 2012 at 11:10 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:

>
> On Jun 22, 2012, at 10:19 AM, Jakob Homan wrote:
>
> > This release doesn't look different than the first Kafka release
> > (snappy notwithstanding).
>
> That's not true.  There are a significant number of new jars.
>
> > That was deemed acceptable and so without a
> > lot of new directives, which don't seem to be clear here, so should
> > this one.
> >
> > Binding +1 on RC3.
> >
> > On Fri, Jun 22, 2012 at 8:24 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
> >> Alan,
> >>
> >> I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades,
> the
> >> only added jar in 0.7.1 is the following.
> >> ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
> >>
> >> Snappy is on Apache License 2.0. So, our licenses should be covered.
> >>
> >> Thanks,
> >>
> >> Jun
> >>
> >>
> >> On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <[EMAIL PROTECTED]
> >wrote:
> >>
> >>> It's the PPMC's job to vet these dependencies, not the mentors.  I
> already
> >>> did this once after no one answered my request for help during the
> 0.7.0
> >>> vote.  Someone from the Kafka PPMC needs to step up.  My vote will
> depend
> >>> on the outcome of this check.
> >>>
> >>> BTW, there's a number of duplicate jars.  Not sure if that will be a
> >>> problem.
> >>>
> >>>
> >>> Regards,
> >>> Alan
> >>>
> >>>
> >>> On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:
> >>>
> >>>> Not sure. It's simple enough to check the email archives for my last
> >>> plea.
> >>>>
> >>>> With that said, I was hoping we could kill two birds with one stone.
> >>>>
> >>>>
> >>>> Regards,
> >>>> Alan
> >>>>
> >>>>
> >>>> On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
> >>>>
> >>>>> Did these dependencies change between 0.7.0 and 0.7.1? -C
> >>>>>
> >>>>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <
> [EMAIL PROTECTED]>
> >>> wrote:
> >>>>>>
> >>>>>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
> >>>>>>
> >>>>>>> Hello,
> >>>>>>>
> >>>>>>> This is the third candidate for the second incubator release for
> >>> Apache
> >>>>>>> Kafka, version 0.7.1-incubating.
> >>>>>>>
> >>>>>>> This release fixes the following issues
> >>>>>>>
> >>>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
> >>>>>>>
> >>>>>>> Release artifacts:
> >>>>>>>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
> >>>>>>>
> >>>>>>> The tag to be voted upon (off the 0.7.1 branch):
> >>>>>>>
> >>>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
> >>>>>>>
> >>>>>>> Kafka's KEYS file containing PGP keys we use to sign the release:
> >>>>>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
> >>>>>>>
> >>>>>>> The vote will be open for 72 hours (longer if needed).
> >>>>>>
> >>>>>>
> >>>>>> I need help checking these jars.  What I recommend is that we update
> >>> NOTICE in trunk as we attribute licenses to the jars below.  This way
> we
> >>> still vet the jars, update the NOTICE/LICENSE file in trunk for the
> next
> >>> release, and not force Joe to cut a new release to include the updated
> >>> NOTICE/LICENSE file.
> >>>>>>
> >>>>>> This will make subsequent releases go much easier.
> >>>>>>
> >>>>>> BTW, the keys and signatures are fine.  Tests pass.
> >>>>>>
> >>>>>> (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find  . -name
> >>> "*.jar"
> >>>>>> ./contrib/hadoop-consumer/lib/piggybank.jar
> >>>>>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar
> >>>>>>
> ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar

This is why documenting transitive dependencies is so dangerous.  The set of jars that I got last year is much different.  This list from last year is what was voted upon.  You need to compare the 0.7.1 list of jars against what I presented last year.  You can hunt down that old email using the email archives.
Regards,
Alan

 
On Jun 22, 2012, at 11:19 AM, Jun Rao wrote:

> Alan,
>
> Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
> Extract *.jar, sort them, and compare. I reached the same conclusion as
> Joe: the only new jar is snappy. Other jar differences are all due to jar
> upgrades (are you referring to those?). Could you list any other completely
> new jars that are not included in 0,7.0 already?
>
> Thanks,
>
> Jun
>
>
> On Fri, Jun 22, 2012 at 11:10 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:
>
>>
>> On Jun 22, 2012, at 10:19 AM, Jakob Homan wrote:
>>
>>> This release doesn't look different than the first Kafka release
>>> (snappy notwithstanding).
>>
>> That's not true.  There are a significant number of new jars.
>>
>>> That was deemed acceptable and so without a
>>> lot of new directives, which don't seem to be clear here, so should
>>> this one.
>>>
>>> Binding +1 on RC3.
>>>
>>> On Fri, Jun 22, 2012 at 8:24 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
>>>> Alan,
>>>>
>>>> I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades,
>> the
>>>> only added jar in 0.7.1 is the following.
>>>> ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
>>>>
>>>> Snappy is on Apache License 2.0. So, our licenses should be covered.
>>>>
>>>> Thanks,
>>>>
>>>> Jun
>>>>
>>>>
>>>> On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <[EMAIL PROTECTED]
>>> wrote:
>>>>
>>>>> It's the PPMC's job to vet these dependencies, not the mentors.  I
>> already
>>>>> did this once after no one answered my request for help during the
>> 0.7.0
>>>>> vote.  Someone from the Kafka PPMC needs to step up.  My vote will
>> depend
>>>>> on the outcome of this check.
>>>>>
>>>>> BTW, there's a number of duplicate jars.  Not sure if that will be a
>>>>> problem.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Alan
>>>>>
>>>>>
>>>>> On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:
>>>>>
>>>>>> Not sure. It's simple enough to check the email archives for my last
>>>>> plea.
>>>>>>
>>>>>> With that said, I was hoping we could kill two birds with one stone.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Alan
>>>>>>
>>>>>>
>>>>>> On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
>>>>>>
>>>>>>> Did these dependencies change between 0.7.0 and 0.7.1? -C
>>>>>>>
>>>>>>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <
>> [EMAIL PROTECTED]>
>>>>> wrote:
>>>>>>>>
>>>>>>>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> This is the third candidate for the second incubator release for
>>>>> Apache
>>>>>>>>> Kafka, version 0.7.1-incubating.
>>>>>>>>>
>>>>>>>>> This release fixes the following issues
>>>>>>>>>
>>>>>
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>>>>>>>>>
>>>>>>>>> Release artifacts:
>>>>>>>>>
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>>>>>>>>>
>>>>>>>>> The tag to be voted upon (off the 0.7.1 branch):
>>>>>>>>>
>>>>>
>> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
>>>>>>>>>
>>>>>>>>> Kafka's KEYS file containing PGP keys we use to sign the release:
>>>>>>>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>>>>>>>>
>>>>>>>>> The vote will be open for 72 hours (longer if needed).
>>>>>>>>
>>>>>>>>
>>>>>>>> I need help checking these jars.  What I recommend is that we update
>>>>> NOTICE in trunk as we attribute licenses to the jars below.  This way
>> we
>>>>> still vet the jars, update the NOTICE/LICENSE file in trunk for the
>> next
>>>>> release, and not force Joe to cut a new release to include the updated

Alan,

Shouldn't we always get the same set of jars after build from the 0.7.0
release, whether it's done when 0.7.0 was voted or now?

Thanks,

Jun

On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:

> This is why documenting transitive dependencies is so dangerous.  The set
> of jars that I got last year is much different.  This list from last year
> is what was voted upon.  You need to compare the 0.7.1 list of jars against
> what I presented last year.  You can hunt down that old email using the
> email archives.
>
>
> Regards,
> Alan
>
>
>
>
> On Jun 22, 2012, at 11:19 AM, Jun Rao wrote:
>
> > Alan,
> >
> > Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
> > Extract *.jar, sort them, and compare. I reached the same conclusion as
> > Joe: the only new jar is snappy. Other jar differences are all due to jar
> > upgrades (are you referring to those?). Could you list any other
> completely
> > new jars that are not included in 0,7.0 already?
> >
> > Thanks,
> >
> > Jun
> >
> >
> > On Fri, Jun 22, 2012 at 11:10 AM, Alan D. Cabrera <[EMAIL PROTECTED]
> >wrote:
> >
> >>
> >> On Jun 22, 2012, at 10:19 AM, Jakob Homan wrote:
> >>
> >>> This release doesn't look different than the first Kafka release
> >>> (snappy notwithstanding).
> >>
> >> That's not true.  There are a significant number of new jars.
> >>
> >>> That was deemed acceptable and so without a
> >>> lot of new directives, which don't seem to be clear here, so should
> >>> this one.
> >>>
> >>> Binding +1 on RC3.
> >>>
> >>> On Fri, Jun 22, 2012 at 8:24 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
> >>>> Alan,
> >>>>
> >>>> I compared all dependent jars in 0.7.1 with 0.7.0. Other than
> upgrades,
> >> the
> >>>> only added jar in 0.7.1 is the following.
> >>>> ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
> >>>>
> >>>> Snappy is on Apache License 2.0. So, our licenses should be covered.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jun
> >>>>
> >>>>
> >>>> On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <
> [EMAIL PROTECTED]
> >>> wrote:
> >>>>
> >>>>> It's the PPMC's job to vet these dependencies, not the mentors.  I
> >> already
> >>>>> did this once after no one answered my request for help during the
> >> 0.7.0
> >>>>> vote.  Someone from the Kafka PPMC needs to step up.  My vote will
> >> depend
> >>>>> on the outcome of this check.
> >>>>>
> >>>>> BTW, there's a number of duplicate jars.  Not sure if that will be a
> >>>>> problem.
> >>>>>
> >>>>>
> >>>>> Regards,
> >>>>> Alan
> >>>>>
> >>>>>
> >>>>> On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:
> >>>>>
> >>>>>> Not sure. It's simple enough to check the email archives for my last
> >>>>> plea.
> >>>>>>
> >>>>>> With that said, I was hoping we could kill two birds with one stone.
> >>>>>>
> >>>>>>
> >>>>>> Regards,
> >>>>>> Alan
> >>>>>>
> >>>>>>
> >>>>>> On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
> >>>>>>
> >>>>>>> Did these dependencies change between 0.7.0 and 0.7.1? -C
> >>>>>>>
> >>>>>>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <
> >> [EMAIL PROTECTED]>
> >>>>> wrote:
> >>>>>>>>
> >>>>>>>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
> >>>>>>>>
> >>>>>>>>> Hello,
> >>>>>>>>>
> >>>>>>>>> This is the third candidate for the second incubator release for
> >>>>> Apache
> >>>>>>>>> Kafka, version 0.7.1-incubating.
> >>>>>>>>>
> >>>>>>>>> This release fixes the following issues
> >>>>>>>>>
> >>>>>
> >>
> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
> >>>>>>>>>
> >>>>>>>>> Release artifacts:
> >>>>>>>>>
> >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
> >>>>>>>>>
> >>>>>>>>> The tag to be voted upon (off the 0.7.1 branch):
> >>>>>>>>>
> >>>>>
> >>
> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/
> >>>>>>>>>
> >>>>>>>>> Kafka's KEYS file containing PGP keys we use to sign the release:
> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS

You would think so but that is not the case.  Simply compare my old email against what you get now.
Regards,
Alan

 
On Jun 22, 2012, at 11:49 AM, Jun Rao wrote:

> Alan,
>
> Shouldn't we always get the same set of jars after build from the 0.7.0
> release, whether it's done when 0.7.0 was voted or now?
>
> Thanks,
>
> Jun
>
> On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:
>
>> This is why documenting transitive dependencies is so dangerous.  The set
>> of jars that I got last year is much different.  This list from last year
>> is what was voted upon.  You need to compare the 0.7.1 list of jars against
>> what I presented last year.  You can hunt down that old email using the
>> email archives.
>>
>>
>> Regards,
>> Alan
>>
>>
>>
>>
>> On Jun 22, 2012, at 11:19 AM, Jun Rao wrote:
>>
>>> Alan,
>>>
>>> Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
>>> Extract *.jar, sort them, and compare. I reached the same conclusion as
>>> Joe: the only new jar is snappy. Other jar differences are all due to jar
>>> upgrades (are you referring to those?). Could you list any other
>> completely
>>> new jars that are not included in 0,7.0 already?
>>>
>>> Thanks,
>>>
>>> Jun
>>>
>>>
>>> On Fri, Jun 22, 2012 at 11:10 AM, Alan D. Cabrera <[EMAIL PROTECTED]
>>> wrote:
>>>
>>>>
>>>> On Jun 22, 2012, at 10:19 AM, Jakob Homan wrote:
>>>>
>>>>> This release doesn't look different than the first Kafka release
>>>>> (snappy notwithstanding).
>>>>
>>>> That's not true.  There are a significant number of new jars.
>>>>
>>>>> That was deemed acceptable and so without a
>>>>> lot of new directives, which don't seem to be clear here, so should
>>>>> this one.
>>>>>
>>>>> Binding +1 on RC3.
>>>>>
>>>>> On Fri, Jun 22, 2012 at 8:24 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
>>>>>> Alan,
>>>>>>
>>>>>> I compared all dependent jars in 0.7.1 with 0.7.0. Other than
>> upgrades,
>>>> the
>>>>>> only added jar in 0.7.1 is the following.
>>>>>> ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
>>>>>>
>>>>>> Snappy is on Apache License 2.0. So, our licenses should be covered.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jun
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <
>> [EMAIL PROTECTED]
>>>>> wrote:
>>>>>>
>>>>>>> It's the PPMC's job to vet these dependencies, not the mentors.  I
>>>> already
>>>>>>> did this once after no one answered my request for help during the
>>>> 0.7.0
>>>>>>> vote.  Someone from the Kafka PPMC needs to step up.  My vote will
>>>> depend
>>>>>>> on the outcome of this check.
>>>>>>>
>>>>>>> BTW, there's a number of duplicate jars.  Not sure if that will be a
>>>>>>> problem.
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Alan
>>>>>>>
>>>>>>>
>>>>>>> On Jun 21, 2012, at 12:31 PM, Alan D. Cabrera wrote:
>>>>>>>
>>>>>>>> Not sure. It's simple enough to check the email archives for my last
>>>>>>> plea.
>>>>>>>>
>>>>>>>> With that said, I was hoping we could kill two birds with one stone.
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Alan
>>>>>>>>
>>>>>>>>
>>>>>>>> On Jun 21, 2012, at 11:32 AM, Chris Douglas wrote:
>>>>>>>>
>>>>>>>>> Did these dependencies change between 0.7.0 and 0.7.1? -C
>>>>>>>>>
>>>>>>>>> On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera <
>>>> [EMAIL PROTECTED]>
>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> On Jun 20, 2012, at 9:19 AM, Joe Stein wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> This is the third candidate for the second incubator release for
>>>>>>> Apache
>>>>>>>>>>> Kafka, version 0.7.1-incubating.
>>>>>>>>>>>
>>>>>>>>>>> This release fixes the following issues
>>>>>>>>>>>
>>>>>>>
>>>>
>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html
>>>>>>>>>>>
>>>>>>>>>>> Release artifacts:
>>>>>>>>>>>
>>>> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3
>>>>>>>>>>>
>>>>>>>>>>> The tag to be voted upon (off the 0.7.1 branch):

On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
> This is why documenting transitive dependencies is so dangerous.

Should we stop?

Marvin Humphrey

Alan-

Please recheck your results using the 0.7.0 release and not your email
archives to make sure your process is consistent. Please also let us
know how you're composing your list so your concerns are reproducible.
We can't be chasing ghosts.

Your memory of the 0.7.0 release is dissimilar to my own, where Neha,
Jakob, and others from the Kafka project audited all the jars and
actually nailed down the required process. A portrayal of the project
as relying on its mentors to do this menial work is inaccurate.

Kevan-

Please appreciate that there is universal agreement that (1) listing
and maintaining all transitive dependencies and licenses is a sound
service and (2) listing all dependencies distributed with source code
carry legal requirements w.r.t. the LICENSE and NOTICE files. We
disagree only on (3) the scope of legally required attribution extends
to the transitive closure of dependencies.

Now, a group of us believe that we investigated this thoroughly in the
Kafka 0.7.0 release and- based on its approval- we are exercising the
same procedure to release 0.7.1. If you believe this is mistaken, you
can either go to the trouble to obtain clarification from board@,
legal@, or find a reference that supports your position. Presented
with that evidence, I would reverse my vote. Alternatively, if you
believe the work is important enough regardless of policy, then do it.
The project would be grateful to receive that contribution. -C

On Fri, Jun 22, 2012 at 12:09 PM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
> You would think so but that is not the case.  Simply compare my old email against what you get now.
>
>
> Regards,
> Alan
>
>
> On Jun 22, 2012, at 11:49 AM, Jun Rao wrote:
>
>> Alan,
>>
>> Shouldn't we always get the same set of jars after build from the 0.7.0
>> release, whether it's done when 0.7.0 was voted or now?
>>
>> Thanks,
>>
>> Jun
>>
>> On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:
>>
>>> This is why documenting transitive dependencies is so dangerous.  The set
>>> of jars that I got last year is much different.  This list from last year
>>> is what was voted upon.  You need to compare the 0.7.1 list of jars against
>>> what I presented last year.  You can hunt down that old email using the
>>> email archives.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>>>
>>>
>>> On Jun 22, 2012, at 11:19 AM, Jun Rao wrote:
>>>
>>>> Alan,
>>>>
>>>> Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
>>>> Extract *.jar, sort them, and compare. I reached the same conclusion as
>>>> Joe: the only new jar is snappy. Other jar differences are all due to jar
>>>> upgrades (are you referring to those?). Could you list any other
>>> completely
>>>> new jars that are not included in 0,7.0 already?
>>>>
>>>> Thanks,
>>>>
>>>> Jun
>>>>
>>>>
>>>> On Fri, Jun 22, 2012 at 11:10 AM, Alan D. Cabrera <[EMAIL PROTECTED]
>>>> wrote:
>>>>
>>>>>
>>>>> On Jun 22, 2012, at 10:19 AM, Jakob Homan wrote:
>>>>>
>>>>>> This release doesn't look different than the first Kafka release
>>>>>> (snappy notwithstanding).
>>>>>
>>>>> That's not true.  There are a significant number of new jars.
>>>>>
>>>>>> That was deemed acceptable and so without a
>>>>>> lot of new directives, which don't seem to be clear here, so should
>>>>>> this one.
>>>>>>
>>>>>> Binding +1 on RC3.
>>>>>>
>>>>>> On Fri, Jun 22, 2012 at 8:24 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
>>>>>>> Alan,
>>>>>>>
>>>>>>> I compared all dependent jars in 0.7.1 with 0.7.0. Other than
>>> upgrades,
>>>>> the
>>>>>>> only added jar in 0.7.1 is the following.
>>>>>>> ./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
>>>>>>>
>>>>>>> Snappy is on Apache License 2.0. So, our licenses should be covered.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jun
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 21, 2012 at 9:30 PM, Alan D. Cabrera <
>>> [EMAIL PROTECTED]
>>>>>> wrote:
>>>>>>>
>>>>>>>> It's the PPMC's job to vet these dependencies, not the mentors.  I
>

On Jun 22, 2012, at 3:16 PM, Chris Douglas wrote:

> Alan-
>
> Please recheck your results using the 0.7.0 release and not your email
> archives to make sure your process is consistent. Please also let us
> know how you're composing your list so your concerns are reproducible.
> We can't be chasing ghosts.

Sorry, I may have been vague with my references to the email archives.

My vote on 0.7.0 was based on the the vetting of the list of jars that I published on the mailing list last year.  The current thinking is that we only need to vet the delta of what was voted on for 0.7.0 and what we currently get for 0.7.1.  So, I am using the list of jars that I voted on for 0.7.0 and am getting a delta of more than one jar when I compare it against the jars downloaded for 0.7.1.
Regards,
Alan

 

Alan,

I found the list of jars that you published during the 0.7.0 release. The
new jars in the 0.7.1 release are the following:
commons-cli: AL2
commons-el: AL2
commons-net: AL2
commons-io: AL2
commons-compress: AL2
core: Eclipse Public License 1.0
hsqldb: BSD
jasper-compiler: AL2
jasper-runtime: AL2
jets3t: AL2
jetty: AL2
jetty-util: AL2
jsp: AL2
jsp-api: AL2
kfs: AL2
xmlenc: BSD
rat-core: AL2
rat-tasks: AL2
snappy: AL2

As you can see, they are all Apache compatible licenses.

Thanks,

Jun

On Fri, Jun 22, 2012 at 5:24 PM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:

>
> On Jun 22, 2012, at 3:16 PM, Chris Douglas wrote:
>
> > Alan-
> >
> > Please recheck your results using the 0.7.0 release and not your email
> > archives to make sure your process is consistent. Please also let us
> > know how you're composing your list so your concerns are reproducible.
> > We can't be chasing ghosts.
>
> Sorry, I may have been vague with my references to the email archives.
>
> My vote on 0.7.0 was based on the the vetting of the list of jars that I
> published on the mailing list last year.  The current thinking is that we
> only need to vet the delta of what was voted on for 0.7.0 and what we
> currently get for 0.7.1.  So, I am using the list of jars that I voted on
> for 0.7.0 and am getting a delta of more than one jar when I compare it
> against the jars downloaded for 0.7.1.
>
>
> Regards,
> Alan
>
>

Sorry, this was sitting in my draft box.

Perfect!  Thanks for checking!

+1
Regards,
Alan

 
On Jun 22, 2012, at 6:09 PM, Jun Rao wrote:

> Alan,
>
> I found the list of jars that you published during the 0.7.0 release. The
> new jars in the 0.7.1 release are the following:
> commons-cli: AL2
> commons-el: AL2
> commons-net: AL2
> commons-io: AL2
> commons-compress: AL2
> core: Eclipse Public License 1.0
> hsqldb: BSD
> jasper-compiler: AL2
> jasper-runtime: AL2
> jets3t: AL2
> jetty: AL2
> jetty-util: AL2
> jsp: AL2
> jsp-api: AL2
> kfs: AL2
> xmlenc: BSD
> rat-core: AL2
> rat-tasks: AL2
> snappy: AL2
>
> As you can see, they are all Apache compatible licenses.
>
> Thanks,
>
> Jun
>
> On Fri, Jun 22, 2012 at 5:24 PM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:
>
>>
>> On Jun 22, 2012, at 3:16 PM, Chris Douglas wrote:
>>
>>> Alan-
>>>
>>> Please recheck your results using the 0.7.0 release and not your email
>>> archives to make sure your process is consistent. Please also let us
>>> know how you're composing your list so your concerns are reproducible.
>>> We can't be chasing ghosts.
>>
>> Sorry, I may have been vague with my references to the email archives.
>>
>> My vote on 0.7.0 was based on the the vetting of the list of jars that I
>> published on the mailing list last year.  The current thinking is that we
>> only need to vet the delta of what was voted on for 0.7.0 and what we
>> currently get for 0.7.1.  So, I am using the list of jars that I voted on
>> for 0.7.0 and am getting a delta of more than one jar when I compare it
>> against the jars downloaded for 0.7.1.
>>
>>
>> Regards,
>> Alan
>>
>>