Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 2013-10-07, at 7:03 AM, Thanh Ha wrote: > > I've been meaning to write something up about this but haven't had the time. > If you use the commandline there's a handy python script [1] that makes the > Gerrit experience a little easier. > > The gist of it is that it's a bunch of shortcuts

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

btw. I will second that figuring out the right steps for submitting to gerrit driven projects is a pain compared to "raw" git. I know I got a few contributions stranded/stalled because I had to fight with gerrit and borked custom instructions on how to set it up. I'm sure its pretty awesome onc

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

AM To: Cross project issues mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit Doug Schaefer mailto:dschae...@qnx.com>> wrote on 10/04/2013 06:47:08 PM: > No they're not. I can't see any w

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

This was not about developers reviewing the changes. As I mentioned upfront, I find gerrit very useful code review tool. I still believe learning Gerrit is a berrier for prospect m2e contributors that are not familiar with it. As long as m2e is not forced to accept contributions through Gerrit, I

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 07/10/13 09:51 AM, John Arthorne wrote: Doug Schaefer wrote on 10/04/2013 06:47:08 PM: > No they're not. I can't see any way that patches in bugzilla are easier > than gerrit. It's one "Push to Gerrit" and one "Publish and Submit" clicks > away from getting a contribution made and accepted

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

Doug Schaefer wrote on 10/04/2013 06:47:08 PM: > No they're not. I can't see any way that patches in bugzilla are easier > than gerrit. It's one "Push to Gerrit" and one "Publish and Submit" clicks > away from getting a contribution made and accepted. The "Submit" button is a bit dangerous that

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

ject issues > Date: Friday, 4 October, 2013 5:24 PM > To: "cross-project-issues-dev@eclipse.org" < > cross-project-issues-dev@eclipse.org> > > Subject: Re: [cross-project-issues-dev] Making your project more > openŠhowto enable Gerrit > > On 10/04/2013 09:00 PM, Ian

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

rg>" mailto:cross-project-issues-dev@eclipse.org>> Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit On 10/04/2013 09:00 PM, Ian Bull wrote: I'm not sure how the more experienced Gerrit users deal with this. I don't consider myself as an

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

No they're not. I can't see any way that patches in bugzilla are easier than gerrit. It's one "Push to Gerrit" and one "Publish and Submit" clicks away from getting a contribution made and accepted. And can't help wonder that these two statements aren't related in some way: "m2e has no plans to a

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 10/04/2013 09:00 PM, Ian Bull wrote: I'm not sure how the more experienced Gerrit users deal with this. I don't consider myself as an expert, but I generally try to keep discussion related to use-case, test scenario and possible designs on the Bugzilla, and put discussions about code itself

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

Hi This seems backwatds. To my way of thinking Gerrit should be making GIT and Bugzilla better. If it tries to replace them it is sure to leave a lot of users disappointed and irritated. Therefore once the Gerrit ping-pong is complete, the Gerrit results should be transferred in their entir

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On Fri, Oct 4, 2013 at 12:00 PM, Ian Bull wrote: > I really like the flow that Gerrit provides. Pushing commits is easier than > creating patchs and uploading them. However, I find with Gerrit (or our use > of Gerrit) is that the discussion is now spread across multiple mediums. > Bugs / feature r

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

er >> with gerrit? >> >> -Original Message- >> From: cross-project-issues-dev-boun...@eclipse.org [mailto: >> cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor Fedorenko >> Sent: October-04-13 1:54 PM >> To: cross-project-issues-dev@e

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

inal Message- > From: cross-project-issues-dev-boun...@eclipse.org [mailto: > cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor Fedorenko > Sent: October-04-13 1:54 PM > To: cross-project-issues-dev@eclipse.org > Subject: Re: [cross-project-issues-dev] Making your

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On Behalf Of Igor Fedorenko > Sent: October-04-13 1:54 PM > To: cross-project-issues-dev@eclipse.org > Subject: Re: [cross-project-issues-dev] Making your project more > openŠhowto enable Gerrit > > Yes. Patches attached to bugzilla are easier. > > -- > Regards, > Igor >

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor Fedorenko Sent: October-04-13 1:54 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit Yes. Patches attached to

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

...@eclipse.org] On Behalf Of Igor Fedorenko Sent: October-04-13 1:54 PM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit Yes. Patches attached to bugzilla are easier. -- Regards, Igor On 2013-10-04 12:25 PM, Mickael

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

jetty generally finds this to be the case as well -- jesse mcconnell jesse.mcconn...@gmail.com On Fri, Oct 4, 2013 at 12:54 PM, Igor Fedorenko wrote: > Yes. Patches attached to bugzilla are easier. > > -- > Regards, > Igor > > > On 2013-10-04 12:25 PM, Mickael Istria wrote: > >> On 10/04/2013

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

Yes. Patches attached to bugzilla are easier. -- Regards, Igor On 2013-10-04 12:25 PM, Mickael Istria wrote: On 10/04/2013 06:08 PM, Igor Fedorenko wrote: m2e has no plans to accept gerrit contributions, at least not for now. I'm curious: Why is this so? Did you find a process that makes cont

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

git-format-patch formatted patches attached to bugzilla is the only way to contribute to m2e and I generally review contributions for the next milestone build. So my statement was strictly related to accepting contributions through gerrit or any other means except bugzilla for that matter. I simp

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

In my defense, the push to Git had two major motivators: 1) CVS is no longer supported and has--as I understand it--several major open bugs that aren't being addressed 2) With the introduction of Git, something had to go; Webmaster does not have infinite resources.

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 10/04/2013 06:08 PM, Igor Fedorenko wrote: m2e has no plans to accept gerrit contributions, at least not for now. I'm curious: Why is this so? Did you find a process that makes contributing easier than it is by Gerrit? -- Mickael Istria Eclipse developer at JBoss, by Red Hat

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

Igor, I think folks generally should have a choice about using gerrit, but I'm wondering if you're statement below is stronger. I.e., do you mean "m2e has no plans to accept contributions"? If the project intends to accept contributions and the source is maintained in a git repo, I'm not

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

the eTrice project is already running a HIPP with Gerrit trigger. It's just great! It significantly reduced the time I spend with reviews -Henrik Am 04.10.2013 16:22, schrieb Doug Schaefer: > I almost wonder if we should just enable Gerrit for all projects. That's what > we do internally here fo

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

m2e has no plans to accept gerrit contributions, at least not for now. Having gerring enabled for m2e will be confusing. -- Regards, Igor On 2013-10-04 10:22 AM, Doug Schaefer wrote: I almost wonder if we should just enable Gerrit for all projects. That's what we do internally here for all git

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

On 10/04/2013 04:22 PM, Doug Schaefer wrote: I almost wonder if we should just enable Gerrit for all projects. That's what we do internally here for all git repos that feed into product. It's great for all the reasons you mention Ed. I can already imagine the various posts from Wayne on blogs/T

Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

I almost wonder if we should just enable Gerrit for all projects. That's what we do internally here for all git repos that feed into product. It's great for all the reasons you mention Ed. The thing I like most about it is the verification jobs in co-ordination with Hudson. You have so much mor