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

List:       kde-community
Subject:    Re: Invent/gitlab, issues and bugzilla
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2019-07-03 5:47:03
Message-ID: CA+XidOE5YvJFQsqXVsotEcuCtb67pv8VxuQe+_HgV6EpYckxTA () mail ! gmail ! com
[Download RAW message or body]

On Wed, 3 Jul 2019, 00:56 Luigi Toscano, <luigi.toscano@tiscali.it> wrote:

> Hi,
>

Hi Luigi,


> one of the main point of the gitlab migration has been so far the
> replacement
> for phabricator. We didn't discuss about bug tracking.
>
> Despite this, I've seen a few projects using issues as replacement for
> bugzilla.
>
>
> We can all debate which is better, whether bugzilla or the gitlab issues,
> but
> please consider that:
>
> - having to ways to report a bug makes like of everyone more complicated
> for
> users reporting bug who need to find the proper place, and for bug triager
>
> - drkonqi still continue to report to bugzilla. Future versions of drkonqi
> can
> be fixed to support the new system and we would need also a proxy for older
> versions of drkonqi, but until such thing exist, a migration is out of
> question.
>

Or just apply the 2 year rule - it would mean waiting 2 years after
shipping a Dr Konqi with support for the new way though.


>
> My suggestion right now is to disable issues completely, or if they need
> to be
> enable to allow us to replace phabricator tasks, then to reduce their
> scope to
> this.
>

The intention originally when we started planning the migration to Gitlab
was that issues within Gitlab would be treated as an equivalent to
Phabricator Tasks - ie. for internal discussions only.

While I know there are people who do want to investigate the possibility of
dropping Bugzilla at some point, that is not something we are pursuing at
this time, and the intention is most certainly for user facing reports to
continue being done using bugs.kde.org (Bugzilla).


> --
> Luigi
>

Regards,
Ben

>

[Attachment #3 (text/html)]

<div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Wed, 3 Jul 2019, 00:56 Luigi Toscano, &lt;<a \
href="mailto:luigi.toscano@tiscali.it">luigi.toscano@tiscali.it</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi,<br></blockquote></div></div><div \
dir="auto"><br></div><div dir="auto">Hi Luigi,</div><div dir="auto"><br></div><div \
dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 \
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
one of the main point of the gitlab migration has been so far the replacement<br>
for phabricator. We didn&#39;t discuss about bug tracking.<br>
<br>
Despite this, I&#39;ve seen a few projects using issues as replacement for \
bugzilla.<br> <br>
<br>
We can all debate which is better, whether bugzilla or the gitlab issues, but<br>
please consider that:<br>
<br>
- having to ways to report a bug makes like of everyone more complicated for<br>
users reporting bug who need to find the proper place, and for bug triager<br>
<br>
- drkonqi still continue to report to bugzilla. Future versions of drkonqi can<br>
be fixed to support the new system and we would need also a proxy for older<br>
versions of drkonqi, but until such thing exist, a migration is out of \
question.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Or \
just apply the 2 year rule - it would mean waiting 2 years after shipping a Dr Konqi \
with support for the new way though.</div><div dir="auto"><br></div><div \
dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 \
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
<br>
My suggestion right now is to disable issues completely, or if they need to be<br>
enable to allow us to replace phabricator tasks, then to reduce their scope to<br>
this.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">The \
intention originally when we started planning the migration to Gitlab was that issues \
within Gitlab would be treated as an equivalent to Phabricator Tasks - ie. for \
internal discussions only.</div><div dir="auto"><br></div><div dir="auto">While I \
know there are people who do want to investigate the possibility of dropping Bugzilla \
at some point, that is not something we are pursuing at this time, and the intention \
is most certainly for user facing reports to continue being done using <a \
href="http://bugs.kde.org">bugs.kde.org</a> (Bugzilla).</div><div \
dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
-- <br>
Luigi<br></blockquote></div></div><div dir="auto"><br></div><div \
dir="auto">Regards,</div><div dir="auto">Ben</div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div>



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