reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Development process on Apache infrastructure
Date Fri, 24 Oct 2014 06:03:16 GMT
Hi Markus,

I have been using Github and Apache recently on Tika and OODT
which are inherently SVN projects ‹ you can simply do #1 in your
list below. I would simply make sure there is a JIRA issue, then
what you do is when you commit to Git@ASF, you say ³this closes
#X² where X is the PR #. That will automatically close out the
pull request on Github. I also then put the rev # in JIRA and
then resolve the issue.

HTH!

Cheers,
Chris


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Markus Weimer <weimer@apache.org>
Reply-To: "dev@reef.incubator.apache.org" <dev@reef.incubator.apache.org>
Date: Wednesday, October 22, 2014 at 8:27 AM
To: "dev@reef.incubator.apache.org" <dev@reef.incubator.apache.org>
Subject: Development process on Apache infrastructure

>Hi,
>
>later today, I will take the GitHub repositories read-only such that
>Sergiy
>can work the git magic of fusing the Wake, Tang and REEF repositories into
>one which will then be pushed onto ASF infrastructure.
>
>Once there, we need to agree on a development cycle. To set the stage for
>that discussion, consider how we structured work on GitHub:
>
>   - Any material work was to be filled as an issue before starting to
>   code.
>   - We never commit to master. Use pull requests instead.
>   - We don't self-commit these pull requests but instead assign them to
>   another committer.
>
>I'd like to preserve as much of that process as possible, as it has served
>us well in the past. And these self-imposed rules have some natural match
>on ASF infrastructure:
>
>   - We file a JIRA issue before starting any material work.
>   - We never commit to master.
>   - We don't self-merge changes to master.
>
>Where I am unclear is how changes get staged for review. I see two options
>for this:
>
>   1. Create a branch with the changes, push it to ASF GitHub and
>reference
>   that branch in the JIRA when we ask for a code review.
>   2. Post a patch to JIRA
>
>Which one do we want to do? Is there a third? Maybe the mentors can way in
>on this?
>
>Thanks,
>
>Markus


Mime
View raw message