[coreboot] [RFC]Using gerrit for patch management (and jenkins for QA)
paulepanter at users.sourceforge.net
Wed Jun 1 11:01:21 CEST 2011
Am Mittwoch, den 01.06.2011, 10:44 +0200 schrieb Patrick Georgi:
> Am 01.06.2011 09:31, schrieb Paul Menzel:
> > Am Dienstag, den 31.05.2011, 20:55 +0200 schrieb Patrick Georgi:
> >> I'm officially sick and tired of patchwork. Or from losing patches to
> >> the mailing list.
> > does that happen so often?
> More than 100 patches unhandled, with some of them duplicates/iterations
> that must be tracked down manually.
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.
> > Since you write Web tool, I am wondering if it is still possible to
> > review patches on the list and to manipulate it using email or the
> > command line.
> No bridge to mail exists at this time. I think it would also be hard to
> map properly.
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.
They would probably need to create an account, log in every time and do
some clicks before they can review something. The main developers need
to commit to and embrace that new work flow.
I am doing no coreboot development and therefore do not care much. But
the main developers (maybe also AMD) should be asked directly.
> But feel free to try.
No time and no intentions to do so.
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the coreboot