e Storm messaging layer pluggable, and plan to use
> > Netty (which is licensed under Apache License v2) as our default
> messaging
> > plugin (while keep 0MQ as an optional plugin).
> >
> > == Cryptography ==
> >
> > We do not expect Storm to be a controll
gt; >>> licensed directly to the Apache foundation through our signed
> Individual
> >>> Contributor License Agreements for all committers on the project.
> >>>
> >>> Yahoo! is also willing to move Storm-on-YARN code from github to be a
> >>&g
on entering Apache, Yahoo! will sign over copyright to Apache
> foundation.
> >>
> >> == External Dependencies ==
> >>
> >> To the best of our knowledge, all of Storm dependencies (except 0MQ/JMQ)
> >> are distributed under Apache compatible licenses. Upon a
Dave,
I would take some issue with your comments here.
If you look at what is happening right now, the entire Drill team is
focussed on making a release and particularly focussed on getting the IP
issues right. There have been several release candidates posted and the
community members have been
rialization plugins … Storm provides plugins for
> plain-object serialization and blowfish encryption.
>
> == Required Resources ==
>
> === Mailing lists ===
>
> * storm-user
> * storm-dev
> * storm-commits
> * storm-private (with moderated subscriptions)
>
> ==
On Thu, Sep 12, 2013 at 1:37 PM, Marvin Humphrey wrote:
> Thanks to Dave for his long record of contributing as a shepherd.
>
Indeed.
And thanks to Dave for checking out Drill. More eyes on a project is
always a good thing.
On Thu, Sep 12, 2013 at 12:54 PM, Dave Fisher wrote:
> Sorry for any consternation. Best of luck. I do think that once your
> podling does release that TLP status should come soon.
>
I would say that we have a little more practice needed in incubator. But
the progress is happening.
One issue t
We've held a vote on drill-dev to release the first milestone release.
The vote thread can be found here:
http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E
The vote passed with
4 x +1 binding votes
7
Lest anybody not understand my implicit vote:
+1 (binding)
On Tue, Sep 17, 2013 at 5:13 PM, Dave Fisher wrote:
> Wonderful.
>
> On Sep 17, 2013, at 3:29 PM, Ted Dunning wrote:
>
> > We've held a vote on drill-dev to release the first milestone release.
> >
>
eteness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
>
>
> On Wed, Sep 18, 2013 at 6:24 AM, Grant Ingersoll
> wrote:
> > +1, binding
> >
> > On Sep 17, 2013, at 6:29 PM, Ted Dunning wrote:
&
Thanks for reviewing at all! Even more thanks for reviewing when you
should be sleeping.
On Wed, Sep 18, 2013 at 12:40 PM, Benson Margulies wrote:
> On Wed, Sep 18, 2013 at 11:42 AM, Ted Dunning
> wrote:
> > Benson,
> >
> > The disclaimer is in the README now:
>
&
This vote has been open for nearly 24 hours out of 72 hours and has just
over 48 hours to run.
This is a tickler in case somebody wants to vote, but has been distracted.
The current tally is 4 binding +1, 1 ambiguous, none against.
On Tue, Sep 17, 2013 at 3:29 PM, Ted Dunning wrote:
> We
, Dave Brondsema wrote:
> Do you have a KEYS file posted somewhere besides within the release?
>
> On 09/17/2013 06:29 PM, Ted Dunning wrote:
> > We've held a vote on drill-dev to release the first milestone release.
> >
> > The vote thread can be f
ame before a product is published:
> http://www.apache.org/**foundation/marks/naming.html<http://www.apache.org/foundation/marks/naming.html>
> I don't see why Drill is an exception, but maybe I have missed something.
>
> Until I know more, I need to -1 this.
>
> Thanks!
ear the name before a product is published:
> http://www.apache.org/**foundation/marks/naming.html<http://www.apache.org/foundation/marks/naming.html>
> I don't see why Drill is an exception, but maybe I have missed something.
>
> Until I know more, I need to -1 this.
>
> T
ed to -1 this.
>
> Thanks!
>
>
>
> On Tue, Sep 17, 2013 at 03:29:46PM -0700, Ted Dunning wrote:
>>
>>> We've held a vote on drill-dev to release the first milestone release.
>>>
>>> The vote thread can be found here:
>>>
>>>
This vote has closed and has passed according to majority vote because it
has at least 3 +1 votes and more +1 than -1 votes.
The final tally is this:
*Binding +1 votes*
Ted Dunning
Steve Loughran
Benson Margulies
Grant Ingersoll
Henry Saputra
Isabel Drost-Fromm
*Binding -1 votes*
Christian
On Sun, Oct 6, 2013 at 9:28 PM, Roman Shaposhnik wrote:
> If my shepherding perspective is any indication this has been quite chronic
> (although this month feels particularly bad). I think you're absolutely
> right
> in suggesting that we should try and address this somehow.
>
One thing that ha
On Fri, Oct 11, 2013 at 12:11 PM, Christian Grobmeier
wrote:
> company. I would therefore like to verify that, in order to contribute the
>> project to ASF, they will be required to sign a Corporate CLA, and a
>> Software Grant Agreement.
>>
>
> yes, the company will need to sign a software grant
On Thu, Nov 7, 2013 at 11:13 AM, Marvin Humphrey wrote:
> The Incubator has a fundamental structural flaw: it lacks a mechanism to
> reward merit earned by individual podling contributors. Instead, we teach
> people to hate the Incubator by placing their projects at the mercy of
> Mentors. Our M
+1 (binding)
On Thu, Nov 7, 2013 at 9:32 PM, Patrick Hunt wrote:
> +1 Accept Twill into the Incubator
>
> Patrick
>
> On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann wrote:
> > The discussion about the Weave proposal has calmed. As the outcome of the
> > discussion, we have chosen a new name
First few words should read "A disclaimer ..."
I blame a combo of jet lag and *really* slow net link. Not the guy who hit
send without proofing, of course.
On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning wrote:
>
> I disclaimer to clarify that the 0.9.0 release is neither an Ap
+1 (binding)
On Thu, Dec 5, 2013 at 3:42 PM, Anil Gupta wrote:
> +1
>
> Hope to see Phoenix in Apache family.
>
> Sent from my iPhone
>
> > On Dec 5, 2013, at 1:43 PM, Stack wrote:
> >
> > Discussion of the Phoenix proposal has settled since its original
> > posting on November 7th. Feedback
On Mon, Dec 9, 2013 at 5:45 AM, Matt Franklin wrote:
> Christian is right. We are watching the lists and follow the discussions,
> but do look for DISCUSS, VOTE, or MENTOR flags especially.
>
>
> On Thu, Dec 5, 2013 at 3:07 AM, Christian Grobmeier >wrote:
>
> > Taylor,
> >
> > your mentors shoul
A point which is often missed by new comers is that votes aren't final
until they vote closes and is tallied.
That allows a vote that uncovers a serious defect to trigger a bunch of
defecting votes (if the vote isn't just canceled)
On Thu, Dec 12, 2013 at 11:02 AM, Doug Cutting wrote:
> On Thu
+1 Binding
On Tue, Dec 31, 2013 at 1:19 PM, Joe Stein wrote:
> +1 (non-binding)
>
> Awesome! Happy New Year!!!
>
> - Joe Stein
>
>
> On Dec 31, 2013, at 3:48 PM, Roman Shaposhnik wrote:
>
> > On Tue, Dec 31, 2013 at 12:39 PM, Jakob Homan wrote:
> >> Incubator-
> >>
> >> Following the discussi
The standard rules all apply to GSoC students. They should do their code
in as close to the standard way as possible (which would have precluded the
code being outside at this point) and they should file and ICLA if they do
enough to warrant it.
On Wed, Jan 8, 2014 at 4:32 AM, Alexander Broekhu
Too many people will read that as Jena, the city in Thuringia.
https://en.wikipedia.org/wiki/Jena
-1
On Mon, Jan 13, 2014 at 1:57 PM, Andy Seaborne wrote:
> On 13/01/14 20:25, Bertrand Delacretaz wrote:
>
>> On Mon, Jan 13, 2014 at 5:36 PM, Bertrand Delacretaz
>> wrote:
>>
>>> On Mon, Jan
+1
On Fri, Jan 31, 2014 at 6:04 PM, Matei Zaharia wrote:
> Hi folks,
>
> The Apache Spark community has VOTEd to graduate from the Apache incubator
> (vote thread: http://s.apache.org/kq, discussion thread:
> http://s.apache.org/aEQ).
>
> I’m now calling an official IPMC VOTE to make this happ
+1 (binding)
These wrinkles are not as big as they appear. For instance, the issue with
some committers not noticing that their accounts were live is actually due to a
better submission and review process than most tlp's exhibit.
The spark community has more of the apache spirit in it than mos
On Sat, Feb 8, 2014 at 7:42 PM, sebb wrote:
> > WDYT?
>
> Non-trivial; maintaining the meta-data needed to accurately generate
> the NOTICE file is likely to require more effort than writing the
> NOTICE file itself.
>
Actually, this sounds like a case where the effort for any individual
projec
On Mon, Feb 10, 2014 at 7:01 AM, Sergio Fernández <
sergio.fernan...@salzburgresearch.at> wrote:
> On 10/02/14 14:49, Daniel Gruno wrote:
>
>> I would suggest you create a new JIRA ticket with this _wish_ and label
>> is as Git+Wilderness, and I'll try to figure out whether we can support
>> this
+1 (binding)
On Tue, Feb 11, 2014 at 3:52 AM, Alex Karasulu wrote:
> +1 (binding)
>
>
> On Tue, Feb 11, 2014 at 6:50 AM, Mosharaf Chowdhury <
> mosharafka...@gmail.com
> > wrote:
>
> > +1
> >
> > --
> > Mosharaf Chowdhury
> > http://www.mosharaf.com/
> >
> >
> > On Mon, Feb 10, 2014 at 8:45 P
+1 (binding)
On Sat, Feb 15, 2014 at 11:43 AM, Joseph Schaefer wrote:
> I would say that is the right approach, and
> that this vote should continue on.
>
> On Feb 15, 2014, at 2:34 PM, P. Taylor Goetz wrote:
>
> > Hi Joseph,
> >
> > Thank you very much for the clarification.
> >
> > After ch
The basic idea is that you have to have the right to incorporate the code
and be able to demonstrate that right.
For example #1, you can switch your contributions to ASL2 and be good, but
you may have problems with the contributions of the others unless the
contributions are trivial.
For example
yeah.
What Joe said.
On Mon, Feb 17, 2014 at 4:27 PM, Joseph Schaefer wrote:
> Judgement call depending on what you might
> consider a reasonable size for a minor fix
> versus an independent work (e.g. new module).
> The larger the patch the more likely you should
> consider having the author f
Sebastian Schelter is a new mentor for Drill and needs wiki write
permissions to sign off on monthly reports.
At his request, I have marked the report for this month, but he would like
to be able to do it himself before the next report.
Can somebody help by giving him permissions? I copied him s
Thanks Nick.
That's why I copied him.
On Tue, Mar 11, 2014 at 10:20 AM, Nick Burch wrote:
> On Tue, 11 Mar 2014, Ted Dunning wrote:
>
>> Sebastian Schelter is a new mentor for Drill and needs wiki write
>> permissions to sign off on monthly reports.
>>
>&
e - fabian.hue...@tu-berlin.de
> * Daniel Warneke - warn...@posteo.de
> * Robert Metzger - metrob...@gmail.com
> * Ufuk Celebi - u.cel...@fu-berlin.de
> * Aljoscha Krettek - aljoscha.kret...@gmail.com
> * Kostas Tzoumas - kostas.tzou...@tu-berlin.de
> * Sebastian Schelter
On Sun, Mar 30, 2014 at 10:26 AM, Sebastien Goasguen wrote:
> Maybe 'stratosphere' is too generic to be able to get trademarks
> established down the road.
>
That is a significant issue that will need to dealt with during incubation.
Good trademarks are very difficult to come up with.
Edward,
Sub-projects are generally frowned on. Incubator projects can graduate
eventually to a top-level project, but starting a project as a sub is not
so good. The incubator docs on this are pretty good reading.
But if the committer community for your real-time BSP is (or can be) the
same as
gt; use of git/github. We request a writeable git repo git://
> git.apache.org/incubator-optiq, and mirroring to be set up to github
> through INFRA.
>
> === Issue Tracking ===
>
> Optiq currently uses the github issue tracking system associated with its
> github repo: https://github.com/
gt;
> === Source control ===
>
> The Optiq team would like to use git for source control, due to our current
> use of git/github. We request a writeable git repo git://
> git.apache.org/incubator-optiq, and mirroring to be set up to github
> through INFRA.
>
> === Issue Trackin
On Thu, May 1, 2014 at 10:19 PM, Kasper Sørensen <
kasper.soren...@humaninference.com> wrote:
> - Can you explain or link to more information about the type inference you
> mention?
>
The type inferencing is used by Drill.
The problem is that strong typing is normally required to parse SQL
state
On Fri, May 9, 2014 at 8:03 PM, Ashutosh Chauhan wrote:
> [X] +1 Accept Optiq into the Incubator
> [ ] +0 Indifferent to the acceptance of Stratosphere
> [ ] -1 Do not accept Optiq because ...
>
The appearance of Stratosphere is a clear typo.
I still vote to accept.
I am working with the Drill team to help them get the report in. The
community is very active with >200 Jiras reported and fixed in the last 30
days.
The problem with the report is likely due to the fact that the community
member who has been creating the reports (Ellen Friedman) has been diverte
Also, with a very new project, it is important to know that they have done
releases before coming to Apache.
On Sun, Jun 8, 2014 at 6:46 PM, Marvin Humphrey
wrote:
> On Sun, Jun 8, 2014 at 6:08 PM, John D. Ament
> wrote:
>
> > If anyone from Flink can answer... as well as IPMC members.
> >
>
l project didn't reported after I
> have
> nudged them on the dev@ list and Ted Dunning forwarded the reminder from
> the
> board.
>
> Cos
>
> On Sat, Jun 07, 2014 at 10:50AM, John D. Ament wrote:
> > Hi all
> >
> > Don't forget, board report
Drill should probably be in that category as well.
300 issues resolved last 30 days, lots of contributors.
They have about as much stuff happening as HBase.
On Tue, Jun 10, 2014 at 6:13 PM, John D. Ament
wrote:
> Marvin,
>
> What do you think about listing storm under ready to graduate inste
On Tue, Jun 10, 2014 at 6:33 PM, John D. Ament
wrote:
> On Tue, Jun 10, 2014 at 9:28 PM, Ted Dunning
> wrote:
> > Drill should probably be in that category as well.
> >
> > 300 issues resolved last 30 days, lots of contributors.
> >
> > They have ab
On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposhnik wrote:
> One thing that I noticed in the report is that the detailed
> metrics around releases are missing. Do folks think
> there's a value in having them?
>
What metrics do you mean?
The metrics that really matter are up-take of the new versio
Good point. Thanks for clarifying.
Yes. I think that those metrics are an excellent measure of community
health.
On Wed, Jun 11, 2014 at 1:55 PM, Roman Shaposhnik wrote:
> On Wed, Jun 11, 2014 at 1:50 PM, Ted Dunning
> wrote:
> > On Wed, Jun 11, 2014 at 1:38 PM, Roman Shaposh
+1 for retirement (binding)
On Fri, Jun 13, 2014 at 1:23 PM, John D. Ament
wrote:
> +1 Please go ahead and retire from the incubator. (binding)
>
> On Fri, Jun 13, 2014 at 2:36 PM, Joe Brockmeier wrote:
> > Hi all,
> >
> > Per recent discussions on general@[1] and s4-dev@ [2], I went ahead a
This is a vote thread, not a discussion thread. Read the earlier messages
which are included in this thread for more context.
On Mon, Jun 16, 2014 at 2:02 PM, abiola balogun wrote:
> Why do u say so and who are you?
>
> Sent from my iPhone
>
> > On Jun 16, 26 Heisei, at 8:18, abiola balogun w
On Wed, Jun 18, 2014 at 11:14 PM, Roman Shaposhnik wrote:
> To this end, I'd like to prose a very simplistic criteria
> for a potential retirement from the incubator: unless both
> of of the following applies project get put to a retirement
> IPMC vote:
>* there has been a release in the past
On Wed, Jun 18, 2014 at 11:46 PM, Alexander Broekhuis wrote:
> as the retirement criteria would IMO be too harsh for Celix when we
> started.
>
In a similar vein, Drill currently has about the same number of commits and
mail messages as Hive does, but hasn't had a release in a while. They have
I think that this is a serious problem for Tez graduation. So far, Tez has
been essentially a one-company show and essentially all of the participants
are there because of their day jobs.
It doesn't seem like it has to be that way, but it also doesn't seem like
there are organic drives to push it
Chris
Regardless of whether it is an explicit requirement to have some specific level
of diversity, there is a requirement that the group demonstrate community
building.
The page in question may be incorrect, but as it stands it does not appear that
a diverse community has been built.
I a
My position on this sort of thing has shifted a whole lot over the last few
years. I used to be very careful about offending bots but after dealing
hundreds of these accounts on MapR user facing sites, I am way less sympathetic.
Kudos for humanity but I recommend not losing much sleep here.
On Sun, Jun 22, 2014 at 9:33 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:
> >Regardless of whether it is an explicit requirement to have some specific
> >level of diversity, there is a requirement that the group demonstrate
> >community building.
>
> I'm also sympathetic to
he other mentors on the project can step up and have some
> insight
> into the below. I look forward to the discussion.
>
>
> Cheers,
> Chris
>
>
> -Original Message-
> From: Ted Dunning
> Reply-To: "general@incubator.apache.org"
> Date: M
I will look as soon as possible. I am on a trip right now and am occupied with
day job stuff >12 hours a day.
If you don't hear from me in a short time, move forward based in your best
judgment. I trust the group to consider my impressions and to think about what
merit they may (or may not) h
On Mon, Jun 23, 2014 at 2:23 PM, Bikas Saha wrote:
> Community building is an organic process that grows on its own accord.
>
Really, I was going to run away for a bit, but my feeling is that this
statement is amazingly naive about how communities are built.
Community doesn't just happen. Comm
I feel your pain!
Sent from my iPhone
> On Jun 28, 2014, at 7:39, Marvin Humphrey wrote:
>
> Others are going to have to step up their game.
>
> Marvin Humphrey
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.
+1
On Tue, Jul 1, 2014 at 7:16 AM, Alan Gates wrote:
> +1.
>
> Alan.
>
> Hitesh Shah
> June 30, 2014 at 9:16 PM
> Hello folks
>
> Tez entered incubation in February, 2013. Since then, we have made
> progress towards graduation[1]. The Tez community recently voted positively
> towards gradu
On Wed, Jul 16, 2014 at 1:20 AM, Chris Douglas wrote:
> > So, I am fond of Henry's hope that the project will solicit a more
> diversified
> > set of mentors and initial committers.
>
> The committer and PPMC list should be honest. If there is no
> diversity, that fact must be visible for it to b
Sounds right to me.
As a separate matter of etiquette and community building, it is usually
good form for mentors to vote last during the community vote and first in
the IPMC vote.
On Thu, Jul 24, 2014 at 8:44 PM, P. Taylor Goetz wrote:
> My interpretation (and it's just that) is:
>
> Exampl
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
065058fff2ccc8cc806c5b2
> optiq:
>
> https://github.com/jacques-n/optiq/commit/4508b617bd3ffed2840055fe16e6684e1c0a35d7
>
> Hopefully this satisfies the need to document the source references for
> third party dependencies within the Apache Drill 0.4.0 release.
>
> thanks,
>
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
tion of the Board of Directors as the chair
> > of the Apache Storm Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Storm Project; and be it further
> >
> > RESOLVED,
Ted missed seeing the dev@ vote, else he (I) would have voted +1.
On Mon, Aug 18, 2014 at 7:11 PM, P. Taylor Goetz wrote:
> Yes. But Ted voted in this general@/IPMC thread. Arvind's vote was in the
> dev@storm/PPMC thread.
>
> -Taylor
>
> > On Aug 18, 2014, at 9:38 PM, Henry Saputra
> wrote:
On Wed, Sep 3, 2014 at 1:05 PM, Marvin Humphrey
wrote:
> So how about creating the web form but having it generate text which can be
> inserted into the wiki template? That would allow us to tune the web
> interface without committing to the new format.
>
+1
A simple interface to copy/paste th
+1 (binding)
Others have checked signatures and conducted functional tests (and noted
tiny discrepancies on the web-site build instructions). I have used this
software from the master branch quite recently. As such, I focussed on
non-functional aspects of the distro.
This looks like a very clea
Is the new process documented somewhere?
On Mon, Sep 8, 2014 at 3:17 PM, sebb wrote:
> On 7 September 2014 20:31, Jacques Nadeau wrote:
> > As I understand the release guidelines, one is not allowed to put
> something
> > on dist.apache.org until after a release vote by the Incubator PMC
> a
documentation?
On Mon, Sep 8, 2014 at 4:27 PM, John D. Ament
wrote:
> Ted,
>
> Do you mean more than here:
>
> [1]: http://www.apache.org/dev/publishing-maven-artifacts.html
> [2]: http://www.apache.org/dev/release.html#host-rc
>
> On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning
alternatives?
On Mon, Sep 8, 2014 at 4:27 PM, John D. Ament
wrote:
> Ted,
>
> Do you mean more than here:
>
> [1]: http://www.apache.org/dev/publishing-maven-artifacts.html
> [2]: http://www.apache.org/dev/release.html#host-rc
>
> On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning
This is easier if you start from the template report that is on the wiki
page.
http://wiki.apache.org/incubator/September2014
Note that the deadline has passed already, so you will likely be asked to
file your report next month.
Some things that I don't see in this report are:
- the amount of t
Last time I had to figure this out, this link was the key:
http://www.apache.org/dev/pmc.html#SVNaccess
On Thu, Sep 11, 2014 at 2:23 PM, P. Taylor Goetz wrote:
> We (Storm) have added a few committers/PPMC members, but they aren’t
> listed under the project on people.apache.org.
>
> Poking t
There is a strong phonetic similarity to Apache Drill, a project in the
same general domain.
Is the Grill name already baked in (pun intended)?
On Fri, Sep 19, 2014 at 7:24 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:
> Thank you Sharad. So I could use this system for r
Both Lens and Blend are nice names. Nice connotations as well.
I am slightly stunned by a quick search on the name Lens. I only found one
software package with that name (and it was for lens calibration so far
from databases). A name like that is usually massively over used.
This might be a re
> Thanks
> Sharad
>
> On Tue, Sep 23, 2014 at 12:04 AM, Ted Dunning
> wrote:
>
> > Both Lens and Blend are nice names. Nice connotations as well.
> >
> > I am slightly stunned by a quick search on the name Lens. I only found
> one
> > software
Drill uses standard sorts of CI infrastructure.
Lens (was Grill) is something I don't know about and they are the ones who
might have something unusual.
On Fri, Sep 26, 2014 at 12:44 PM, David Nalley wrote:
> > currently employed by SoftwareAG. Raghavendra Singh from InMobi has built
> > the
On Mon, Sep 29, 2014 at 8:52 PM, William A. Rowe Jr.
wrote:
> The HTTP Server PMC has succeeded in working through these issues without
> evicting a project member, and continuing to make progress.
>
There is a lot of credit due for this.
Of course, there are different stresses on each project.
On Tue, Sep 30, 2014 at 3:46 AM, Greg Stein wrote:
> To the concrete question, the Subversion project never calls a strict
> [VOTE] for new committers or PMC members. We discuss first, and that sets
> the direction. People throw out +1 messages, but that is "sure, make it so"
> rather than a true
The unit test was only on Java 1.8. That problem will be resolved in the
next release which will be in roughly a month from now. The current
primary target of Drill is 1.7.
The number of reviewers for the release is an indication of how the
community doesn't view Java 1.8 as a critical platform
On Tue, Oct 7, 2014 at 8:41 AM, jan i wrote:
> It seems (from the vote thread) you already have solved the problem, but
> dont want to wait for a respin, can you please at least explain why the
> project is under such a time constraint, that 72 hours is too long to wait
> to make good quality.
>
On Tue, Oct 7, 2014 at 2:46 PM, jan i wrote:
> > 4.) And lastly, as Julian mentioned on the thread that the set of fixes
> > might not be complete yet,
> > I think we need more time before we can merge these changes in to a
> release
> > with confidence to
> > support a new platform.
> >
>
> I ag
On Tue, Oct 7, 2014 at 2:46 PM, jan i wrote:
> My intentation was to raise a concern, NOT to block the release (I did on
> purpose give a 0 and not -1). I am sorry if you feel its an over-statement,
> but honestly for me failing unit tests and not checking a version
> dependency (in case of older
+1 (binding)
I have downloaded the code, compiled and run the tests.
I also checked all checksums, and verified the signatures. I also verified
that the signing key was signed by people I trust (and indeed, by me as
well) and correctly propagated to the gpg key servers.
I also reviewed in both
in - those just have to wait a month. Only for critical
> correctness issues did I delay a release for a few days.
>
> Obviously that is just my opinion.)
>
> Thanks.
>
> -- Lars
>
>
>
>
>
> From: Ted Dunning
>
The standard practice has been drifting in incubator-land.
When I brought this up previously, I was told a few things,
1) the notices required by BSD like licenses apparently should appear in
the LICENSE file.
2) notices in the source distribution only need to include things that are
included in
Sean,
Are you talking about the src distribution after doing the build?
Before doing the build or after [mvn clean], there are no jars in the
distribution.
Videlicet:
*ted:apache-drill-0.6.0-incubating-src$ mvn -q
cleanted:apache-drill-0.6.0-incubating-src$ find . -name
'*.jar'ted:apache-d
ting.tar.gz
>
> This contains the third-party jar files in jars/.
>
> I assume http://www.apache.org/dev/licensing-howto.html is still the
> law of the land so to speak and indicates that lots of these things
> need to be in NOTICE.
>
>
> On Oct 10, 2014 9:24 PM, "Ted
some third-party uber jars
> here like hive-exec, but I don't see a Drill uber jar. Maybe that
> counts; maybe it's safer just to populate NOTICE appropriately. Or,
> avoid shipping copies of all these jars directly?
>
> On Sat, Oct 11, 2014 at 7:17 AM, Ted Dunning
> w
In any case, the NOTICE files included in every jar are preserved. The
Drill binary release complies *exactly* with the language "include a
readable copy of the attribution notices contained within such NOTICE file".
There is no violation of OSS licenses going on here.
On Sat, Oct 11, 2014 at
On Sat, Oct 11, 2014 at 6:51 AM, Sean Owen wrote:
> Yes it means greater downstream burden, yes it may have originated
> from a 'hack', but that doesn't seem to make the license not say what
> it says. Obviously I'd rather not have to do this either.
>
It is a tortured and patently incorrect rea
On Sat, Oct 11, 2014 at 8:13 AM, Sean Owen wrote:
> Here's another example. Drill distributes Netty 4.0.20, which is AL2
> licensed and contains a substantial NOTICE file with stuff like ...
>
>
> ---
> This product conta
On Sat, Oct 11, 2014 at 8:13 AM, Sean Owen wrote:
> Unfortunately, Netty does not include NOTICE.txt in any of its jars
> for you. This text does not appear therefore in the Drill binary
> distro. At least, I grepped up and down the whole distro and didn't
> see it, and it's not in the Netty jars
On Sat, Oct 11, 2014 at 11:08 AM, Sean Owen wrote:
> On Sat, Oct 11, 2014 at 7:02 PM, Ted Dunning
> wrote:
> > Netty's artifacts ("its distribution") do not include a notice. Thus,
>
> They most certainly do. Please download the distribution of Netty 4.0.20:
&
1 - 100 of 707 matches
Mail list logo
