From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, Adam Jackson <ajax@redhat.com>
Cc: "DRM maintainer tools announcements, discussion,
and development" <dim-tools@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
IGT development <igt-dev@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [igt-dev] RFC: Migration to Gitlab
Date: Fri, 24 Aug 2018 09:52:05 +0300 [thread overview]
Message-ID: <878t4wmf3e.fsf@intel.com> (raw)
In-Reply-To: <20180822160645.GC2340@intel.com>
On Wed, 22 Aug 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
>> On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
>>
>> > - Sticking to fdo bugzilla and disabling gitlab issues for at least
>> > drm-intel for the time being. Doing that migration in the same go is a
>> > bit much I think. Reassignment across bugzilla and gitlab will be an
>> > issue.
>>
>> Can you elaborate a bit on the issues here? The actual move-the-bugs
>> process has been pretty painless for the parts of xorg we've done so
>> far.
>
> I guess there is nothing against moving the bugs there. The concern is only on
> doing everything at once.
No, it's not just that.
We have some automation using the bugzilla APIs directly, and
someone(tm) needs to figure out how this should work with gitlab. Maybe
we have a better chance of doing things with gitlab's APIs, maybe we can
reduce our dependence on external logic altogether.
We have special "i915 platform" and "i915 features" fields in
bugzilla. We use a mailing list default assignee. Some of us use the
"whiteboard" and "keywords" fields. Etc.
I don't think figuring all this out is rocket science, but someone needs
to actually do it, and get our workflows straightened out *before* we
flip the switch. I'm just trying to figure out if that is a blocker to
migrating the repos.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-24 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 11:44 [igt-dev] RFC: Migration to Gitlab Daniel Vetter
2018-08-22 13:05 ` [igt-dev] [Intel-gfx] " Sean Paul
2018-08-22 13:13 ` [Intel-gfx] [igt-dev] " Jani Nikula
2018-08-22 14:19 ` Adam Jackson
2018-08-22 16:06 ` Rodrigo Vivi
2018-08-22 16:37 ` Daniel Stone
2018-08-22 17:01 ` Rodrigo Vivi
2018-08-24 6:52 ` Jani Nikula [this message]
2018-08-24 12:03 ` Daniel Vetter
2018-08-22 14:44 ` Daniel Vetter
2018-08-22 16:33 ` Daniel Stone
2018-08-22 15:02 ` Emil Velikov
2018-08-22 16:29 ` Daniel Stone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t4wmf3e.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ajax@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox