From: Egon Willighagen <egon.willighagen@gm...> - 2012-02-05 10:26:25
with the recent problems with SourceForge with patches not being
downloadable, I decided it was finally time to explore Gerrit a bit
more, to estimate how much time it would be to set up.
The problem *always* is that you get very far, which makes you not
just estimate the amount of work, but also in fact doing the work...
there goes your night rest, weekend, and family life... oh well.
OK, bottom line is, I think I got it all figured out just now, and
just managed to submit a dummy patch for review with my local
I will talk to my colleagues at BiGCaT and set this up in
Maastricht... there will be a learning curve, mostly for Rajarshi and
me, to tweak the workflow. For users, nothing much will change, though
we should have 'git tutorial' sections to get more users provide
patches as git patches...
I anticipate a few months of testing in which we use Gerrit internally
(well, everyone who wants to try) for all patches, but remain using
SourceForge as formal user-oriented frontend. All patches we get via
other channels we can push to Gerrit ourselves. Things to figure out
is how to automate signing off, set up automatically pushing of
approved patches to GitHub, etc, etc... Avogadro even seem to have a
bot that automatically tests of patches compile... that would be very
Dr E.L. Willighagen
Department of Bioinformatics - BiGCaT
Maastricht University (http://www.bigcat.unimaas.nl/)