Migrating Wayland & Weston to GitLab

[Daniel Stone]

Hi,

On 4 June 2018 at 09:05, Daniel Stone <daniel at fooishbar.org> wrote:
> On 29 May 2018 at 10:59, Daniel Stone <daniel at fooishbar.org> wrote:
>> I would like to get the issues migrated as well. In order to do that
>> though, we need some more fixes to the 'bztogl' migration tool we've
>> been using to push issues from Bugzilla to GitLab, as well as do
>> migrations for some other projects which requested to migrate their
>> issues a while ago. It also needs a fair few changes in order to fix
>> support for Phabricator task import as well.
>>
>> But even once those are done, we need to clean up the bugs we're
>> importing. The plan is to only import open bugs: closed bugs will stay
>> in Bugzilla/Phabricator forever as a read-only archive, and GitLab
>> will only have new active issues. I think a sensible transition plan
>> would be for us to aim to do the import at the end of June, which
>> means sweeping through all our open bugs before then, closing them if
>> they're no longer useful or just cleaning up titles/etc to be helpful
>> in future.
>
> I've started cleaning through the bugs as well, but would appreciate
> all the help I can get.

With the cleanup and the Phabricator script fixing having gone far
more quickly than thought, I've migrated the issues now:
    https://gitlab.freedesktop.org/wayland/wayland/issues/
    https://gitlab.freedesktop.org/wayland/weston/issues/

If you want to be notified of all new issues, you can 'watch' either
the Wayland group or the Wayland/Weston projects. You can also
subscribe to individual issue labels (e.g. 'DRM/KMS backend') if you
want to keep a narrow interest. Currently the issues are a bit of a
hodge-podge, but I intend to spend some time going through applying
relevant labels and fixing up any stray formatting etc. Of course, any
help with the triage would be excellent: simply add the labels you
think are relevant and drop the 'bugzilla' label so we know it's been
reasonably triaged.

Cheers,
Daniel