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

List:       freedesktop-xorg-devel
Subject:    Re: gitlab migration
From:       Adam Jackson <ajax () redhat ! com>
Date:       2018-08-20 15:46:17
Message-ID: 90c1d59714228db89b591468154d5fa6d22b4d54.camel () redhat ! com
[Download RAW message or body]

On Mon, 2018-06-11 at 12:33 +0200, Michel Dänzer wrote:

> As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating
> these to GitLab for Git and patch review.
> 
> However, I'm not sure what to do about bugs/issues. My first thought was
> to allow creating new issues in GitLab and disable creating new reports
> in Bugzilla, but not to migrate existing reports from Bugzilla. However,
> it still happens fairly often that a report is initially filed against
> the Xorg drivers, even though it's actually an issue in the X server,
> Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to
> stick to Bugzilla until at least the X server and Mesa have moved to
> GitLab for issue tracking, to hopefully allow moving such misfiled issues.

I've hacked up the migration script to allow moving individual issues
by bug number instead of matching a whole product/component [1]. This
has already been useful to sort out some of the junkdrawer components
like App/Other. Running the script does require someone with supercow
powers on both sides, but I'm happy to do so as needed.

With that in mind, I think it may be time to enable issues and merge
requests for xserver, and disable the remaining (server) bz components
for new issues. Any objections?

[1] - https://gitlab.freedesktop.org/freedesktop/bztogl/merge_requests/1

- ajax
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
[prev in list] [next in list] [prev in thread] [next in thread]