Re: [e4-dev] Mandatory Gerrit usage for the e4 project?

[Markus Alexander Kuppe <e4-dev_eclipse.org@xxxxxxxxxxx>]

On 11/22/2013 09:28 AM, Daniel Rolka wrote:
> Sometimes Gerrit unnecessary slows down the development - you have to
> wait for somebody to review your changes. It is especially painful when
> you handle several things simultaneously. So I'm not sure if we should
> make it the mandatory step after becoming the committer. Every committer
> can take the code and adjust it when they think sth can be
> refactored/implement in better way. Hovever I think, introducing some
> changes that can break sth/block sb or you are not sure if it is correct
> we should commit changes via Gerrit to get feedback,
> 
> +1 for preparing the Hudson build for E4

+1 to make it a judgment call for the individual committer (people over
process).

M.