On 10/07/2014 04:01 PM, Chuck Bridgham
wrote:
Would it be possible
for you to help
us define the set of instructions for project leads to
follow(like you
started below)? You can use me (JavaEE project) as an example.
Sure.
So the steps for Java EE would be:
1. Open a bug against the Eclipse Foundation > Community >
Gerrit component (
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Gerrit
) asking for usage of Gerrit for your project repository. Specify on
the bug that for the moment you'd like to keep the ability for
committers to push directly and to be able to bypass review. This
requires project lead to give a +1. Here is an example:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=421975
2. After webmaster processed your request, the current Git repo
becomes read-only. So in order to be able to push, you'll need to
update to the new Gerrit repo URLs such as
ssh://user@xxxxxxxxxxxxxxx:29418/jeetools/webtools.javaee.git
3. If you use SSH you'll need to upload your public key to Gerrit:
https://git.eclipse.org/r/#/settings/ssh-keys
4. Configure notifications to be informed of incoming reviews by
watching the jeetools/webtools.javaee project:
https://git.eclipse.org/r/#/settings/projects
And IIRC that's all. Then committers can directly push to the repo
as they're used to -just the underlying URL is different-, and
contributors (and committers who want to get code reviewed before
merging) can push with "git push gerrit HEAD:refs/for/master".
This JSDT wiki page shows the instructions for contributors to push
a change for review:
https://wiki.eclipse.org/JSDT/Development#Gerrit_Reviews
A next step would be to set up jobs to have Hudson validation Gerrit
patches, but this can be done in a next iteration.
I won't be able to attend next call (if it's still on Thursday 8pm
in Europe), but I'll take any question that could help you to move
to Gerrit as high-priority, so feel free to bug me as much as
necessary.
Cheers,
|