Yes, thanks, Andrew, this is useful (especially the detail in the
committer's guide). Couple of questions:
- Does the github mirror get behind the Apache git repo leading to problems
(perhaps leading to the committer having to do extra merges)?
- Have you considered trying to automate the "Commiting the changes to the
ASF repo" steps, or perhaps it's not worth it?
Regards,
James


On Fri, Jan 31, 2014 at 11:42 AM, Andrew Phillips <[email protected]>wrote:

> Hi James!
>
>
>  The Phoenix project has recently come into incubation from it's former
>> life
>> as a Github project. I believe jclouds went through this same transition,
>> so I'm looking to get some advice from you. What's the best development
>> methodology folks have found for collaborative development when your
>> source
>> of truth is an Apache git repo?
>>
>
> Roughly, our setup is as follows:
>
> 1) Apache Git repos are the source of truth
> 2) A Jenkins mirror job creates mirrors of all Apache repos in GitHub
> regularly
> 3) Contributors are encouraged to submit PRs "the GitHub way"
> 4) Reviews happen via GitHub
> 5) Once the review is complete, changes are merged by a committer via a
> patch or cherry-pick (there are a couple of styles)
>
> The committers' guide might also contain some useful info for you:
>
> http://wiki.apache.org/jclouds/Committers%20Guide
>
> Is this the kind of thing you're looking for..?
>
> Regards
>
> ap
>

Reply via email to