Mailing-List: contact dev-help@spark.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of matei.zaharia@gmail.com
 designates 209.85.160.45 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Licensing check] Spark 0.8.0-incubating RC1
From: Matei Zaharia <matei.zaharia@gmail.com>
In-Reply-To: 
 <CADWPM3iGZ9BgFSgS69Kjr8=5Z7yfsLs9DqeLnD0V91WFOyuXEw@mail.gmail.com>
Date: Tue, 3 Sep 2013 19:08:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <83DAF1FE-D306-4546-91F7-397E2F7CE8E6@gmail.com>
References: <1BD53DE4-3E0A-4FD9-A4BA-72B982349B24@gmail.com>
 <8D1610F3-F593-4323-957C-86886959ED69@gmail.com>
 <CAAsvFPkFMn0qKKXwguZ6bb4T+ScF-SMpsNc4BuNS+qkbpQ=8Xg@mail.gmail.com>
 <C84BB78E-4FCE-4EC4-9135-753A32FBC363@gmail.com>
 <CAAsvFPmAgD0bE4XtCNnTiqss0TWw6uGCZ1q9piPPrm8iCO4W9A@mail.gmail.com>
 <B4C7C66B-A667-41F4-97EC-E04D92046FA8@gmail.com>
 <CAAsvFP=KWqO6pRjLVnBbq_tm+2DS_kjLQu4JRrHTNuVuUwJ3iA@mail.gmail.com>
 <CADWPM3iGZ9BgFSgS69Kjr8=5Z7yfsLs9DqeLnD0V91WFOyuXEw@mail.gmail.com>
To: dev@spark.incubator.apache.org

Yes, please do the PRs against the GitHub repo for now.

Matei

On Sep 3, 2013, at 4:57 PM, Evan Chan <ev@ooyala.com> wrote:

> Sorry one more clarification.
>=20
> For doc pull requests for 0.8 release, should these be done against
> the existing mesos/spark repo, or against the mirror at
> apache/incubator-spark ?
> I'm hoping to clear up a couple things in the docs before the release =
this week.
>=20
> thanks,
> -Evan
>=20
>=20
> On Tue, Sep 3, 2013 at 2:25 PM, Mark Hamstra <mark@clearstorydata.com> =
wrote:
>> Okay, so is there any way to get github's compare view to be happy =
with
>> differently-named repositories?  What I want is to be able to compare =
and
>> generate a pull request between
>> github.com/apache/incubator-spark:masterand, e.g.,
>> github.com/markhamstra/spark:myBranch and not need to create a new
>> github.com/markhamstra/incubator-spark.  It's bad enough that the
>> differently-named repos don't show up in the compare-view drop-down
>> choices, but I also haven't been able to find a hand-crafted URL that =
will
>> make this work.
>>=20
>>=20
>>=20
>> On Tue, Sep 3, 2013 at 1:38 PM, Matei Zaharia =
<matei.zaharia@gmail.com>wrote:
>>=20
>>> Yup, the plan is as follows:
>>>=20
>>> - Make pull request against the mirror
>>> - Code review on GitHub as usual
>>> - Whoever merges it will simply merge it into the main Apache repo; =
when
>>> this propagates, the PR will be marked as merged
>>>=20
>>> I found at least one other Apache project that did this:
>>> http://wiki.apache.org/cordova/ContributorWorkflow.
>>>=20
>>> Matei
>>>=20
>>> On Sep 3, 2013, at 10:39 AM, Mark Hamstra <mark@clearstorydata.com> =
wrote:
>>>=20
>>>> What is going to be the process for making pull requests?  Can they =
be
>>> made
>>>> against the github mirror =
(https://github.com/apache/incubator-spark),
>>> or
>>>> must we use some other way?
>>>>=20
>>>>=20
>>>> On Tue, Sep 3, 2013 at 10:28 AM, Matei Zaharia =
<matei.zaharia@gmail.com
>>>> wrote:
>>>>=20
>>>>> Hi guys,
>>>>>=20
>>>>>> So are you planning to release 0.8 from the master branch (which =
is at
>>>>>> a106ed8... now) or from branch-0.8?
>>>>>=20
>>>>> Right now the branches are the same in terms of content (though I =
might
>>>>> not have merged the latest changes into 0.8). If we add stuff into
>>> master
>>>>> that we won't want in 0.8 we'll break that.
>>>>>=20
>>>>>> My recommendation is that we start to use the Incubator release
>>>>> doc/guide:
>>>>>>=20
>>>>>> http://incubator.apache.org/guides/releasemanagement.html
>>>>>=20
>>>>> Cool, thanks for the pointer. I'll try to follow the steps there =
about
>>>>> signing.
>>>>>=20
>>>>>> Are we "locking" pull requests to github repo by tomorrow?
>>>>>> Meaning no more push to GitHub repo for Spark.
>>>>>>=20
>>>>>> =46rom your email seems like there will be more potential pull =
requests
>>> for
>>>>>> github repo to be merged back to ASF Git repo.
>>>>>=20
>>>>> We'll probably use the GitHub repo for the last few changes in =
this
>>>>> release and then switch. The reason is that there's a bit of work =
to do
>>>>> pull requests against the Apache one.
>>>>>=20
>>>>> Matei
>>>=20
>>>=20
>=20
>=20
>=20
> --=20
> --
> Evan Chan
> Staff Engineer
> ev@ooyala.com  |