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

List:       kde-core-devel
Subject:    Re: Proposal for using gitlab for kdereview process
From:       Jonathan Riddell <jr () jriddell ! org>
Date:       2023-07-04 12:32:59
Message-ID: CANX=XXMh-KkzUjikbcHUa-fWf7o+_=BJCw+QzxFARBWxMdcXCQ () mail ! gmail ! com
[Download RAW message or body]

I've gone ahead an updated the Sanity checklist and updated the kde review
policy to ask people to make an Issue on gitlab labelled "KDE Review
Request"

https://community.kde.org/Policies/Application_Lifecycle#kdereview

So you can now find kdereview requests at
https://invent.kde.org/dashboard/issues?sort=created_date&state=opened&label_name[]=KDE+Review+Request

Which is linked from
https://community.kde.org/Policies/Application_Lifecycle#kdereview

I'll open Issues for outstanding kdereview projects.

Jonathan



On Mon, 19 Jun 2023 at 19:55, Jonathan Riddell <jr@jriddell.org> wrote:

> Seems using issues is more intuitive so I'll ask for a global group label
> for issues and update the process docs for kdereview and incubator.
>
> Incubator suggestion is here
> https://discuss.kde.org/t/proposal-kde-invent-based-incubator-process/
>
> Jonathan
>
>
> On Wed, 1 Mar 2023 at 08:27, David Redondo <kde@david-redondo.de> wrote:
>
>> So there are two new kdereview requests using gitlab issues now instead
>> of my
>> more complicated idea of merge requests. I imagined a MR to have
>> advantages
>> for codereview but an issue seems to be less complicated (no need to have
>> an
>> empty orphan branch, etc..), so maybe we should go with that.
>>
>> David
>>
>>
>>

[Attachment #3 (text/html)]

<div dir="ltr"><div>I&#39;ve gone ahead an updated the Sanity checklist and updated \
the kde review policy to ask people to make an Issue on gitlab labelled &quot;KDE \
Review Request&quot;<br></div><div><br></div><div><a \
href="https://community.kde.org/Policies/Application_Lifecycle#kdereview" \
target="_blank">https://community.kde.org/Policies/Application_Lifecycle#kdereview</a></div><div><br></div><div>So \
you can now find kdereview requests at <a \
href="https://invent.kde.org/dashboard/issues?sort=created_date&amp;state=opened&amp;l \
abel_name[]=KDE+Review+Request">https://invent.kde.org/dashboard/issues?sort=created_d \
ate&amp;state=opened&amp;label_name[]=KDE+Review+Request</a></div><div><br></div><div>Which \
is linked from <a href="https://community.kde.org/Policies/Application_Lifecycle#kdere \
view">https://community.kde.org/Policies/Application_Lifecycle#kdereview</a></div><div><br></div><div>I&#39;ll \
open Issues for outstanding kdereview \
projects.</div><div><br></div><div>Jonathan</div><div><br></div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 19 Jun 2023 at 19:55, \
Jonathan Riddell &lt;<a href="mailto:jr@jriddell.org" \
target="_blank">jr@jriddell.org</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Seems using issues is more \
intuitive so I&#39;ll ask for a global group label for issues and update the process \
docs for kdereview and incubator.</div><div><br></div><div>Incubator suggestion is \
here <a href="https://discuss.kde.org/t/proposal-kde-invent-based-incubator-process/" \
target="_blank">https://discuss.kde.org/t/proposal-kde-invent-based-incubator-process/</a></div><div><br></div><div>Jonathan</div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 1 Mar 2023 at 08:27, \
David Redondo &lt;<a href="mailto:kde@david-redondo.de" \
target="_blank">kde@david-redondo.de</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">So there are two new kdereview requests using \
gitlab issues now instead of my <br> more complicated idea of merge requests. I \
imagined a MR to have advantages <br> for codereview but an issue seems to be less \
complicated (no need to have an <br> empty orphan branch, etc..), so maybe we should \
go with that.<br> <br>
David<br>
<br>
<br>
</blockquote></div>
</blockquote></div>



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