Hi all,
Gerrit for SimRel has been widely used by many projects and the
validation checks that come with Simrel have successfully caught a bunch
of issues before the had the opportunity to break the Simultaneous
Release. Gerrit and Code-Review can have an incredible effect on
software quality, many projects and teams enforce it with success. I
don't have metrics, but maybe David can say whether he felt a noticeable
improvement in stability/quality since the inception of Gerrit a few
months ago?
I believe it's the right time to start considering enforcing Gerrit
usage for SimRel: a first implementation would be to have committers
push to refs/for/master instead of master, and would either be reviewed
by someone else, or review themselves their contribution. The Hudson
validation job triggers automatically on any contribution and gives a
vote if the contribution is breaking the build.
What do you think?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
