, 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 Bull wrote:
I'm not sure how the more experienced Gerrit users deal with this.
I
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
October, 2013 9:51 AM
To: Cross project issues
cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto
enable Gerrit
Doug Schaefer dschae...@qnx.commailto:dschae...@qnx.com wrote on 10/04/2013
06
On 2013-10-07, at 7:03 AM, Thanh Ha thanh...@eclipse.org 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
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
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
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
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 for
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
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
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.
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
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
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 i...@ifedorenko.com wrote:
Yes. Patches attached to bugzilla are easier.
--
Regards,
Igor
On 2013-10-04 12:25 PM, Mickael Istria wrote:
On
...@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
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
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
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
cross-project-issues-dev@eclipse.orgmailto: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
19 matches
Mail list logo
