[coreboot] [RFC]Using gerrit for patch management (and jenkins for QA)

Patrick Georgi patrick at georgi-clan.de
Wed Jun 1 11:11:36 CEST 2011

Am 01.06.2011 11:01, schrieb Paul Menzel:
> Well if people would mark there iterations [PATCH v2] or send them as a
> reply, I guess it would be scriptable. But you would have to
> teach/educate the developers.
Only if the tool is able to deduct which patch it is version 2 of.
Once it can do that, we wouldn't need that mark.

> So the question is, if the developers would adapt to this new work flow
> using a Web interface. Most free software developers are used to email
> as far as I know.
There used to be a time where no SCMs (distributed or not) were used.
Traditions are nice and all - until they get in the way.

> The main developers need
> to commit to and embrace that new work flow.
That's why I ask.

> It might be also a good idea to ask that question on the flashrom list,
> since they also use the infrastructure(?) and there are some Google
> folks who maybe have experience with at least Gerrit.
I've been approached by flashrom developers already. There's no issue
with keeping patchwork alive for them (and the mailing lists will
continue to exist anyway).

It's just that for coreboot, the infrastructure doesn't work all that
well - probably because compared to flashrom it's a less integrated package.


More information about the coreboot mailing list