Heads up that 1.6.3 RC2 might be impacted by the change of the JSON.org
licenses to category-x (disallowed dependency license) described in SPARK-18262.
Not sure if I'll have time to evaluate in time to cast a non-binding -1 before
the voting window closes.
-
busbey
On 2016-11-02 19:40 (-0500)
On Fri, May 13, 2016 at 6:37 AM, Tom Graves
wrote:
> So we definitely need to be careful here. I know you didn't mention it but
> it mentioned by others so I would not recommend using LimitedPrivate. I had
> started a discussion on Hadoop about some of this due to the way Spark
> needed to use s
We could switch to the Audience Annotation from Apache Yetus[1], and
then rely on Public for end-users and LimitedPrivate for those things
we intend as lower-level things with particular non-end-user
audiences.
[1]:
http://yetus.apache.org/documentation/in-progress/#yetus-audience-annotations
On
I'd suggest that the hbase-downstreamer project[1] is a better place
for folks to see these examples. There's already an example for spark
streaming that does not rely on any of the new goodness in the
hbase-spark module[2].
Granted, it uses the Spark Java APIs[3], but we'd be glad to have a
scala
Having a PR closed, especially if due to committers not having hte
bandwidth to check on things, will be very discouraging to new folks.
Doubly so for those inexperienced with opensource. Even if the message
says "feel free to reopen for so-and-so reason", new folks who lack
confidence are going to
On Wed, Mar 30, 2016 at 4:33 AM, Steve Loughran wrote:
>
>> On 29 Mar 2016, at 22:19, Michael Segel wrote:
>>
>> Hi,
>>
>> So yeah, I know that Spark jobs running on a Hadoop cluster will inherit its
>> security from the underlying YARN job.
>> However… that’s not really saying much when you thi
the private@spark list is only available to PMC members[1]. Could we
document somewhere (the IntelliJ section of the wiki[2]?) both the current
point of contact and a list of what happens when things get renewed each
year?
That way we could include either a note that the POC should email the key
t
On Wed, Dec 2, 2015 at 3:19 PM, Sean Busbey wrote:
>
>
> On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust
> wrote:
>
>>
>>>
>> The release is theoretically several weeks behind plan on what's
>>> intended to be a fixed release cycle too. Th
On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust
wrote:
>
>>
> The release is theoretically several weeks behind plan on what's
>> intended to be a fixed release cycle too. This is why I'm not sure why
>> today it's suddenly potentially ready for release.
>>
>
> Up until today various committers
Looks good to me. Thanks for helping find a common ground everyone, and
Sean for handling the implementation.
On Mon, Jul 20, 2015 at 2:22 AM, Sean Owen wrote:
> This is done, and yes I believe that resolves the issue as far all here
> know.
>
> http://spark.apache.org/downloads.html
> ->
>
> ht
ions are based on actual Apache
> bylaws and/or legal requirements, and we need to take them seriously.
> Other times they have seemed more subjective and have felt more like
> meddling or stirring up trouble in the community and with a process that is
> actually working very well
Responses inline, with some liberties on ordering.
On Sun, Jul 12, 2015 at 10:32 PM, Patrick Wendell
wrote:
> Hey Sean B,
>
> Would you mind outlining for me how we go about changing this policy -
> I think it's outdated and doesn't make much sense. Ideally I'd like to
> propose a vote to modify
Please note that when the policy refers to "developers" it means the
developers of the project at hand, that is participants on the dev@spark
mailing list.
As I stated in my original email, you're welcome to continue the discussion
on the policy including the definition of developers on general@in
e developer wiki, to keep it out from
> the place all and users look for downloads. What do you think about
> that Sean B?
>
> On Sat, Jul 11, 2015 at 5:34 AM, Sean Busbey wrote:
> > Hi Folks!
> >
> > I noticed that Spark website's download page lists nightly build
Hi Folks!
I noticed that Spark website's download page lists nightly builds and
instructions for accessing SNAPSHOT maven artifacts[1]. The ASF policy on
releases expressly forbids this kind of publishing outside of the dev@spark
community[2].
If you'd like to discuss having the policy updated (i
15 matches
Mail list logo
