I am subscribed to receive the gerrit notifications but others may not be. I do try to be responsive to contributions from gerrit, but some of the contributions I simply do not have the knowledge to handle. For example, native launcher changes.
I've talked to a few at eclipse con this week and it does not appear to be an easy thing to fix at this point to make the gerrit builds work. For the short term we may have to disable the build verification from gerrit. I agree that the situation is not good for contributions. I'm told this is similar to the settings used by the eclipse.platform.runtime git repo by the way. They have similar issues getting the gerrit builds to work. I would love to have them work, but fear some very significant build restructuring would have to occur in order to get it to work.
Lets be clear, right now committers in equinox (and there are not a lot) are not using gerrit to contribute our own contributions to Equinox. In fact we setup our gerrit configuration such that the committers still can commit without going through gerrit.
Mickael Istria ---03/17/2014 06:01:34 PM---On 03/17/2014 11:16 PM, Alex Blewitt wrote: > So yes, itâs clear that the Equinox project doesnât us
From: Mickael Istria <mistria@xxxxxxxxxx>
Date: 03/17/2014 06:01 PM
Subject: Re: [equinox-dev] State of Gerrit jobs
Sent by: equinox-dev-bounces@xxxxxxxxxxx
On 03/17/2014 11:16 PM, Alex Blewitt wrote:
So yes, itâs clear that the Equinox project doesnât use Gerrit.
As a reminder, here is the page where Gerrit users can receive Gerrit notifications to react accordingly: https://git.eclipse.org/r/#/settings/projects
Committers should register for the project they are committers on, it's as important as following Bugzilla notifications.
Maybe Equinox committers just forgot to do so and weren't aware of those incoming reviews and build failures.
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
equinox-dev mailing list