Another proposal for modernization of our infrastructure

Milian Wolff mail at
Mon Feb 2 12:17:21 GMT 2015

On Saturday 31 January 2015 20:56:41 Martin Graesslin wrote:
> On Saturday 31 January 2015 20:37:31 Christoph Feck wrote:
> > On Saturday 31 January 2015 20:07:42 Eike Hein wrote:
> > > [...] Qt is using gerrit and we intend to remain a major stakeholde
> > > in Qt development, which means a sizable number of KDE developers
> > > need to be familiar with gerrit anyway [...]
> > 
> > Excuse me, but if KDE developers will have to follow equivalent steps
> > as described at to
> > contribute, then I predict another big loss of developers.
> I have to agree. Whenever I need to do a change for Qt I need to google for
> how to do it. Including putting serious thought in how the push command must
> look like, how I need to adjust the examples provided and for which
> ref/for/foo it has to be this time. This is something which seriously
> concerns me with the outlook of gerrit. git has a steep learning curve,
> gerrit adds quite some further steepness to it :-(

Just add an alias for the refs, e.g. for 5.4 and dev, then use that in the 
future. `git qpush<tab>` and pick one, that's how I do it. E.g.:

    qpushdev = push gerrit HEAD:refs/for/dev

And yes, this is something that kdesrc-build could automate for us.

The rest of the above is independent of the actual tool. Even with reviewboard 
or phabricator, you'll need to know where to push your change. Bugfix? Latest 
stable release you want to support. New feature? dev.

Milian Wolff
mail at

More information about the kde-core-devel mailing list