Gerrit/Advanced usage

Interview with Chad 1 Feb 2012
Stuff that is in Chad's head.



The process in Git conversion is right, even if the dates are wrong.

hard to use gerrit as viewwc

gerrit has gitweb built in but no urls are easy to find we've talked to Ryan about that, can probably set up a redirect to make that easier

Some stuff we will leave in SVN and not bother migrating because it has been abandoned. Some people will choose to move to github or something. And some ops stuff, Mark et al. are moving it to git piecemeal.

Review-before-merge

this workflow - review-before-merge will also apply to any ext we deploy, as well as any ext author who wants it for their extension. Default is current model -- pushed and automatically merged.

We will defer to whoever is considered the primary author on the extension.

The one exception is i18n commits, which will be able to be pushed without review.

workflow
The diagram is pretty clear. Just needs transcribing.

The gerrit review workflow might change since Roan & Chad are reviewing using git-review that will help us as we use git and gerrit together.

How gerrit works & workflow within gerrit


 * http://wiki.openstack.org/GerritWorkflow


 * http://source.android.com/source/life-of-a-patch.html

Also useful (subtract away GitHub stuff):
 * http://wiki.openstack.org/GerritJenkinsGithub