[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Migrating to the gitlab issue tracker
From: |
Alex Bennée |
Subject: |
Re: Migrating to the gitlab issue tracker |
Date: |
Fri, 30 Oct 2020 10:26:17 +0000 |
User-agent: |
mu4e 1.5.6; emacs 28.0.50 |
John Snow <jsnow@redhat.com> writes:
> On 10/29/20 3:55 PM, Thomas Huth wrote:
>> On 29/10/2020 18.12, John Snow wrote:
>>> On 10/29/20 12:49 PM, Alistair Francis wrote:
>>>> On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck <cohuck@redhat.com> wrote:
>>>>>
>>>>> On Thu, 29 Oct 2020 12:01:27 -0400
>>>>> John Snow <jsnow@redhat.com> wrote:
>>>>>
>>>>>> If you're in the CC list, it's because you are listed in MAINTAINERS.
>>>>>
>>>>> <cleared the cc: list except for qemu-devel :)>
>>>>>
>>>>>>
>>>>>> Paolo's QEMU keynote this morning mentioned the possible use of the
>>>>>> Gitlab issue tracker instead of using Launchpad.
>>>>>>
>>>>>> I'm quite fond of the gitlab issue tracker, I think it works quite well
>>>>>> and it has pretty good and uncomplicated API access to it in order to
>>>>>> customize your workflow if you'd really like to.
>>>>>>
>>>>>> In experimenting with my mirror on gitlab though, I was unable to find a
>>>>>> way to configure it to send issue tracker notifications to the email
>>>>>> list. A move to gitlab would likely mean, then:
>>>>>>
>>>>>> 1. The cessation of (automatic) issue tracker mails to the list
It would miss this feature as sometimes I get wind of things I can track
down. On the other hand there is a fair bit of list noise at the end of
a release when stuff gets closed.
>>>>>> 2. The loss of the ability to update the issue tracker by replying to
>>>>>> said emails
>>>>>> 3. Anyone listed in MAINTAINERS would be expected to have a gitlab
>>>>>> account in order to interact with the issue tracker.
Not a problem for me at least - it's just another (2FA) account.
<snip>
>> So could somebody please enable the issue tracker there, so we can give it a
>> try? Phil? Alex? Stefan? ...?
>>
>> If it works well, I can certainly help to get the links etc. in our website
>> fixed.
>>
>
> Great! You are the primary bug wrangler, so if you are interested in
> trialing it, I am interested in helping!
>
> If we enable the bug tracker, can we please add Thomas and myself as
> 'Reporter' level contributors to QEMU so we can wrangle bugs?
I have enabled the issue tracker and assigned Thomas and you the first
bug.
> Info on permissions: https://docs.gitlab.com/ee/user/permissions.html
>
> There's also an old bug (2 years) about migrating Launchpad to Gitlab,
> but there's been no movement.
>
> https://gitlab.com/gitlab-org/gitlab/-/issues/22600
>
> If we like the results of the trial, we'll need a convincing migration
> strategy.
Can we extract data as a CSV from Launchpad?
--
Alex Bennée
- Re: Migrating to the gitlab issue tracker, (continued)
- Re: Migrating to the gitlab issue tracker, Cornelia Huck, 2020/10/29
- Re: Migrating to the gitlab issue tracker, Alistair Francis, 2020/10/29
- Re: Migrating to the gitlab issue tracker, John Snow, 2020/10/29
- Re: Migrating to the gitlab issue tracker, Kashyap Chamarthy, 2020/10/29
- Re: Migrating to the gitlab issue tracker, Thomas Huth, 2020/10/29
- Re: Migrating to the gitlab issue tracker, John Snow, 2020/10/29
- Re: Migrating to the gitlab issue tracker, Daniel P . Berrangé, 2020/10/30
- Re: Migrating to the gitlab issue tracker, Peter Maydell, 2020/10/30
- Re: Migrating to the gitlab issue tracker, Daniel P . Berrangé, 2020/10/30
- Re: Migrating to the gitlab issue tracker, Peter Maydell, 2020/10/30
- Re: Migrating to the gitlab issue tracker,
Alex Bennée <=
- Re: Migrating to the gitlab issue tracker, John Snow, 2020/10/30
Re: Migrating to the gitlab issue tracker, John Snow, 2020/10/29
Re: Migrating to the gitlab issue tracker, Stefan Hajnoczi, 2020/10/30