Re: [thym-dev] GitHub or Gerrit?

[Gorkem Ercan <gorkem.ercan@xxxxxxxxx>]

Is there a reason that we should choose one. Can we have both? 

I agree with Doug the gerrit verify jobs is great. I have seen them done for PRs with Travis, I wonder if we could do it with HIPP or just use Travis as well. 

--

Gorkem

On Wed, Jul 2, 2014 at 10:48 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

+1. The key selling point for me is the Gerrit verify jobs.

Doug.

---

From: thym-dev-bounces@xxxxxxxxxxx [thym-dev-bounces@xxxxxxxxxxx] on behalf of Mickael Istria [mistria@xxxxxxxxxx]
Sent: Wednesday, July 02, 2014 10:40 AM
To: thym-dev@xxxxxxxxxxx
Subject: [thym-dev] GitHub or Gerrit?

Hi all,

Will Thym use GitHub or Gerrit as Git server?

I would prefere Gerrit for the following reasons:
* You end up with a cleaner history because it doesn't create automatically "Merge" commits, and it has a 1 change = 1 commit model (as opposed to GitHub PR, 1 change = N commits)
* It has better comparison mechanism between the various version of a patch than GitHub has for Pull Request
* It's quite easy to automate build and tests of Gerrit patches and to get CI voting on issues to identify regressions before they're merged. Those build and tests

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
thym-dev mailing list
thym-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/thym-dev