[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: [kde-community] Future Git Plans
From:       Martin Klapetek <martin.klapetek () gmail ! com>
Date:       2014-02-18 13:02:27
Message-ID: CAPLgePpjdFwxBzP51Bjw7zCuiCSWZiv8D8SzpX2wYxjAwZdmXQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Feb 18, 2014 at 1:45 PM, Frederik Gladhorn <gladhorn@kde.org> wrote:

>
>
> I tried working with github for a project, using a workflow of reviewing
> each commit. I personally really disliked it for creating a merge commit
> for each commit, that just clutters up the history (try looking at any
> github project with a few contributors).
>
>
>
> Is this the same with gitlabs or can it cherry-pick after successful
> reviews?
>
>
>
> On the other hand I find dealing with reviewboard quite cumbersome and
> thus this option still looks better to me.
>

Fwiw, the Review Board guys are working on a push-based review system,
bascially a gerrit with RB interface. This is a set of extension scripts
usable with RB 2.0, which brings many other features as well, you can watch
a video of it here: http://vimeo.com/86448355. Also, we can even wire our
own "Push" button into RB, it's quite simple from what I understood and
could merge patches for us without needing to do "git push" ourselves
everytime.

I would personally very much prefer to stay with RB if possible, plus the
devs are really awesome and helpful.

Cheers
-- 
Martin Klapetek | KDE Developer

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Feb 18, 2014 \
at 1:45 PM, Frederik Gladhorn <span dir="ltr">&lt;<a href="mailto:gladhorn@kde.org" \
target="_blank">gladhorn@kde.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><u></u>
 <div style="font-family:monospace;font-size:9pt;font-weight:400;font-style:normal"><div \
class=""> <p style="margin:0px;text-indent:0px"><span \
style="font-family:monospace;font-size:9pt">  </span><br></p> </div><p \
style="margin:0px;text-indent:0px">I tried working with github for a project, using a \
workflow of reviewing each commit. I personally really disliked it for creating a \
merge commit for each commit, that just clutters up the history (try looking at any \
github project with a few contributors).</p>


<p style="margin:0px;text-indent:0px">  </p>
<p style="margin:0px;text-indent:0px">Is this the same with gitlabs or can it \
cherry-pick after successful reviews?</p> <p style="margin:0px;text-indent:0px">  \
</p> <p style="margin:0px;text-indent:0px">On the other hand I find dealing with \
reviewboard quite cumbersome and thus this option still looks better to \
me.</p></div></blockquote><div><br></div><div>Fwiw, the Review Board guys are working \
on a push-based review system, bascially a gerrit with RB interface. This is a set of \
extension scripts usable with RB 2.0, which brings many other features as well, you \
can watch a video of it here:  <a \
href="http://vimeo.com/86448355">http://vimeo.com/86448355</a>. Also, we can even \
wire our own &quot;Push&quot; button into RB, it&#39;s quite simple from what I \
understood and could merge patches for us without needing to do &quot;git push&quot; \
ourselves everytime.</div>

<div><br></div><div>I would personally very much prefer to stay with RB if possible, \
plus the devs are really awesome and \
helpful.</div><div><br></div></div><div>Cheers</div>-- <br><div><span \
style="color:rgb(102,102,102)">Martin Klapetek | KDE  Developer</span></div>


</div></div>



_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

[prev in list] [next in list] [prev in thread] [next in thread]