Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
Received-SPF: pass (athena.apache.org: domain of debasish.das83@gmail.com
 designates 209.85.220.50 as permitted sender)
MIME-Version: 1.0
Date: Sat, 1 Mar 2014 11:28:59 -0800
Message-ID: 
 <CA+B-+fzjYAp2j91gecDWe7vAfDUvO1si8J-tk4wLi0utGSZjcw@mail.gmail.com>
Subject: Development methodology
From: Debasish Das <debasish.das83@gmail.com>
To: dev <dev@spark.incubator.apache.org>
Content-Type: multipart/alternative; boundary=047d7b677694f1467804f390903a

--047d7b677694f1467804f390903a
Content-Type: text/plain; charset=ISO-8859-1

Hi,

We have a mirror repo of spark at our internal stash.

We are adding changes to a fork of the mirror so that down the line we can
push the contributions back to Spark git.

I am not sure what's the exact the development methodology we should follow
as things are a bit complicated due to enterprise stash.

Any suggestions would be great.

I have follow usecases:

1. Ask for a pull request and push the changes from stash mirror upstream
to the spark apache git.

2. I am working on 2 PR that are currently open. What's the best way to
work on those ?
Can I get those PR through the stash mirror of Spark git or those PRs are
only available on github ?

Thanks.
Deb

--047d7b677694f1467804f390903a--