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
>
On 24 June 2012 17:30, Marvin Humphrey wrote:
> On Sun, Jun 24, 2012 at 7:32 AM, sebb wrote:
>> The N&L files only apply to what is included in the release archive itself.
>
> +1
>
>> If there are other dependencies, these can be listed in a
>> DEPENDENCIES or README file.
>
> +1, perfect...
>
>
On Sun, Jun 24, 2012 at 7:32 AM, sebb wrote:
> The N&L files only apply to what is included in the release archive itself.
+1
> If there are other dependencies, these can be listed in a
> DEPENDENCIES or README file.
+1, perfect...
The list of transitive dependencies can also change if differi
Le 6/24/12 4:32 PM, sebb a écrit :
On 24 June 2012 14:11, Emmanuel Lécharny wrote:
AFAICT, the important thing is that those who will download Kafka (or any
other ASF project) can't be fooled when includig it into their own projects.
The N&L files are here to facilitate our user's work, by lis
On 24 June 2012 14:11, Emmanuel Lécharny wrote:
> Le 6/24/12 10:46 AM, Chris Douglas a écrit :
>>
>> Kevan-
>
>
> Hi, jumping on this thread, because we have had similar discussions on
> another incubating project I'm mentoring...
>
>>
>> This argument is logical, but that doesn't make it legal an
Le 6/24/12 10:46 AM, Chris Douglas a écrit :
Kevan-
Hi, jumping on this thread, because we have had similar discussions on
another incubating project I'm mentoring...
This argument is logical, but that doesn't make it legal and thus
required. It is also a constraint foreign to most TLPs, mak
Kevan-
This argument is logical, but that doesn't make it legal and thus
required. It is also a constraint foreign to most TLPs, making its
rigid enforcement in the incubator unfair and arbitrary. Not to be
glib, but you clearly do have time to pursue this broadly and across
the foundation if, in
On Jun 22, 2012, at 6:16 PM, Chris Douglas wrote:
> Kevan-
Hi Chris,
Thanks for elaborating.
>
> Please appreciate that there is universal agreement that (1) listing
> and maintaining all transitive dependencies and licenses is a sound
> service
It's more than "sound". We are required to mee
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:
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 chasi
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
On Jun 22, 2012, at 3:13 PM, Marvin Humphrey wrote:
> On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera
> wrote:
>> This is why documenting transitive dependencies is so dangerous.
>
> Should we stop?
No. The solution is that projects should control their dependencies
(direct/transitive) so
On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera wrote:
> This is why documenting transitive dependencies is so dangerous.
Should we stop?
Marvin Humphrey
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For
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 vote
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 wrote:
> This is why documenting transitive dependencies is so dangerous. The set
> of jars that
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
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
n
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 see
This release doesn't look different than the first Kafka release
(snappy notwithstanding). 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 wrote:
> Alan,
>
> I c
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
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. N
On Jun 21, 2012, at 6:27 PM, Marvin Humphrey wrote:
> At some point, though, IPMC members either need to start voting -1 on any
> incubating RC that has a jar file in it, or someone needs to formally answer
> Roy's argument and explain how binary files can be considered "open source"
> when they
On Thu, Jun 21, 2012 at 4:27 PM, Chris Douglas wrote:
> Your musings on binaries are, as Martin pointed out, not legal arguments but
> preferences for clean downstream consumption.
I think there's been a miscommunication. Kevan and I may place different
weight on documenting licensing for non-bu
+1 on the release.
Run quickstart and unit tests. All good.
Thanks,
Jun
On Wed, 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
>
> htt
No. You have access to the same search functionality. Moreover, given the
criteria that Kafka 0.7.0 was approved under, the burden of proof is on you
to find references. Your musings on binaries are, as Martin pointed out,
not legal arguments but preferences for clean downstream consumption. Even
i
On Jun 21, 2012, at 4:36 PM, Chris Douglas wrote:
> 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 rel
Thanks for the improvements Joe!
I'm still -1 based on the licensing and binary artifacts in your source.
(binding)
--kevan
On Jun 20, 2012, at 12:19 PM, Joe Stein wrote:
> Hello,
>
> This is the third candidate for the second incubator release for Apache
> Kafka, version 0.7.1-incubating.
>
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 n
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, 20
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 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 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.
>>
>>
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
32 matches
Mail list logo
