On 8 August 2014 18:12, Marvin Humphrey wrote:
> Hi Ted,
>
> On Fri, Aug 8, 2014 at 9:44 AM, Ted Dunning wrote:
>> Also, I think that it is important that *all* dependency licenses be
>> documented in the source release. Speaking as a consumer, I need to know
>> what dependencies will come in wh
Hi,
> Justin, would you be willing to review these changes
> once we get them up so that we can make sure we're not making other foolish
> mistakes?
Sure just ping me and I'll take a look - it's reasonably straight forward if
you follow this [1]
Justin
1.http://www.apache.org/dev/licensing-how
Hi Ted,
On Fri, Aug 8, 2014 at 9:44 AM, Ted Dunning wrote:
> Also, I think that it is important that *all* dependency licenses be
> documented in the source release. Speaking as a consumer, I need to know
> what dependencies will come in when I compile the code. Marking the
> dependencies as so
Also, I think that it is important that *all* dependency licenses be
documented in the source release. Speaking as a consumer, I need to know
what dependencies will come in when I compile the code. Marking the
dependencies as source inclusions or as compile time or as test
dependencies or as pack
One additional thought. As I'm thinking more about the NOTICE and LICENSE
files I think it would be really helpful to have some reviews from you guys
much earlier in the process than the next release vote. While the docs are
helpful and we'll do our best, I'm skeptical we'll get it exactly right
Hey guys,
Sorry I didn't see Henry and Justin's comments until just now. Per
Justin's primary concerns about the License stuff: I think we've just made
mistakes in the notice and license files as to exactly how we reference
things. All the category B licenses are mvn binary dependencies (per the
Hi,
> Ah, I saw disclaimer in the website [1] which I thought enough for incubator.
> But checking the branding guide [2] seems like incubator need to
> include DISCLAIMER file along with NOTICE and LICENSE files, so this
> could be blocker?
Given it has 3 +1 votes and a result been called it's r
Ah, I saw disclaimer in the website [1] which I thought enough for incubator.
But checking the branding guide [2] seems like incubator need to
include DISCLAIMER file along with NOTICE and LICENSE files, so this
could be blocker?
I think that is the one that could be blocker, but other probably
cou
(resending as it look like the original email got caught up in moderation)
Hi
-1 binding.
There several issues with LICENSE and NOTICE that need to be fixed/explained
before I'd vote +1. I am concerned about the category B licences in particular.
The required DISCLAIMER file is also missing.
Thanks for all the feedback. I've opened DRILL-1271 to fix the NOTICE
issue for the next release. We'll also work towards synchronizing
releases. I think it may take a bit of time given how quickly each of
these projects are moving. The primary thing we're focused on is making
sure that we work
+1 binding.
In the future, I would like to see you guys move to a synchronized release
cycle and only execute releases against their final versions and not
snapshots. Typically, you need to mess with Maven a lot to make this kind
of release even work.
John
On Tue, Aug 5, 2014 at 3:44 PM, Jacqu
Signatures files looks good
LICENSE looks good
NOTICE file needs to update year to 2014 => not a blocker but please
open ticket to track it
Version looks good
No 3rd party exec files
+1
- Henry
On Mon, Aug 4, 2014 at 7:07 AM, Jacques Nadeau wrote:
> We've held a vote on drill-dev to release th
Hmm
That really is quite different. To add to the mix, the two projects in
question are in the process of entering the Apache incubator. In Optiq's
case, at least, that means that they have made what they have stated to be
their last non-Apache release, but are not yet in a position to make
Hey Ted,
Those SNAPSHOT dependencies are a bit misleading. Because Drill is so
closely coupled to the Optiq and Parquet codebase, we need to generate
separate artifacts. As part of doing monthly releases, it is unfeasible to
bind Drill releases to incorporating of all patches into upstream proje
I checked the source artifact and found several internal SNAPSHOT
dependencies (should be fixed) and one external SNAPSHOT dependency (must
be fixed).
The good news is that the external SNAPSHOT dependency is parquet version
1.5.0-SNAPSHOT. Since parquet 1.5.0 has been released, this should be a
We've held a vote on drill-dev to release the 0.4.0-incubating release of
Apache Drill.
The vote thread can be found here:
http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201407.mbox/%3CCAKa9qD%3DKQURAMcS3RQJbUABSU4%3DDEGSewK2s4MAAidu4c%3DOjBg%40mail.gmail.com%3E
The vote passed with
16 matches
Mail list logo